-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Is your feature request related to a problem? Please describe.
I'm trying to configure an Nx monorepo to house multiple Sanity studio instances. However, there's no way to specify the path to the config file; for my setup these are nested under apps/<project-name>. This results in Sanity looking for a sanity.config.* in the root of my repo, rather than the project folder where I organize my schemas.
Describe the solution you'd like
I'd like to request the ability to set a --config flag to resolve a custom path when provided.
Describe alternatives you've considered
Alternatives that I've tried are running sanity commands from the apps current working directory, however, this doesn't work as the monorepo dependencies are installed in the root of the repo, rather than at the project level. This is because Nx strongly recommends that dependencies be managed in a single, root package.json.
I believe that the changes needed could be applied here:
- Add the logic for reading the
configargument -sanity/cli/src/util/getCliConfig.ts - Add the
configargument -@sanity/cli/src/util/parseArguments.ts
