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
I'm interested in a dynamically generated config file, such as a workspace.js (versus .json).
I've got a repository that will eventually grow to include many projects, with a lot of redundant custom configurations (which would all need to be independently edited, when a change is needed). What would be ideal is to use a workspace.js file which ends up rendering a final configuration by preprocessing a bunch of independent project configurations (which I understand is an upcoming feature), and making any necessary custom modifications.
In the meantime, my plan is to leverage a custom generator to emulate this behavior, and using custom plugins to produce separate config files, instead of adding them to the monolithic workspace.json. One major drawback to this is that any edits made to the workspace.json be overwritten by any number of commands, creating an unintuitive dev experience.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm interested in a dynamically generated config file, such as a
workspace.js
(versus.json
).I've got a repository that will eventually grow to include many projects, with a lot of redundant custom configurations (which would all need to be independently edited, when a change is needed). What would be ideal is to use a
workspace.js
file which ends up rendering a final configuration by preprocessing a bunch of independent project configurations (which I understand is an upcoming feature), and making any necessary custom modifications.In the meantime, my plan is to leverage a custom generator to emulate this behavior, and using custom plugins to produce separate config files, instead of adding them to the monolithic
workspace.json
. One major drawback to this is that any edits made to theworkspace.json
be overwritten by any number of commands, creating an unintuitive dev experience.Beta Was this translation helpful? Give feedback.
All reactions