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
Some CLI tools that rely on configs will do validation on those configs to ensure they are correct. For example Webpack does this:
I'm not entirely sure how this would be achieved, so I thought I'd open that up for discussion. Happy to look into implementing once there is consensus on the best approach.
Code
I would imagine the interface would be something like this:
dojo validate
or for example
dojo build
Throws an error if .dojorc doesn't match a specified schema
The text was updated successfully, but these errors were encountered:
One option would be a dedicated validate command alongside a validate method on the Command interface (which is how eject is handled). Each cli package would specify an optional validate method on the Command object it exports, and at the very least that would be executed with $ dojo validate. Additionally, the command-level validate could also be executed each time the command itself is invoked (e.g., $ dojo build would also validate the "build-app" config).
Enhancement
Some CLI tools that rely on configs will do validation on those configs to ensure they are correct. For example Webpack does this:
I'm not entirely sure how this would be achieved, so I thought I'd open that up for discussion. Happy to look into implementing once there is consensus on the best approach.
Code
I would imagine the interface would be something like this:
dojo validate
or for example
dojo build
Throws an error if
.dojorc
doesn't match a specified schemaThe text was updated successfully, but these errors were encountered: