You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which scope/s are relevant/related to the feature request?
Don't know / other
Information
Currently, the Spartan UI library expects the components.json file to reside in the project root. This hardcoded path limits flexibility, especially for projects with non-standard directory structures or specific configuration management needs. For example, a project might use both Spartan UI and shadcn, with each library requiring its own components.json configuration file. This can lead to conflicts when the same filename is used by different tools.
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue
Yes
No
The text was updated successfully, but these errors were encountered:
Which scope/s are relevant/related to the feature request?
Don't know / other
Information
Currently, the Spartan UI library expects the components.json file to reside in the project root. This hardcoded path limits flexibility, especially for projects with non-standard directory structures or specific configuration management needs. For example, a project might use both Spartan UI and shadcn, with each library requiring its own components.json configuration file. This can lead to conflicts when the same filename is used by different tools.
Describe any alternatives/workarounds you're currently using
No response
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: