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
It would be useful to separate the build steps from the runner in the Build CLI tool, which would provide benefits like:
Separating the configuration will make this tool generic which can use with different projects than Chipmunk.
Avoid having to have a new version of the build tool each time a change in Chipmunk build system happens.
It'll reduce the complexity in the codebase of the CLI tool since the complexity of the build system will be moved a configuration file and the codebase of the tool has to take care parsing those configurations then running the tasks in efficient way providing all the other useful options.
Configuration model
We need to set a configuration model which represents targets and variety of jobs with all their dependencies and custom steps
This configuration must have a version which will be validated by the tool at the start of parsing.
It would be useful to define the model in Rust, then using Serde we can even support verity of formats
Here is a prototype of the configuration model in Json format:
It would be useful to separate the build steps from the runner in the Build CLI tool, which would provide benefits like:
Configuration model
Serde
we can even support verity of formatsHere is a prototype of the configuration model in Json format:
The text was updated successfully, but these errors were encountered: