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
Is your feature request related to a problem or issue you encountered? Please describe.
The current build process when serving a chain always building proto files with the embedded protoc of Ignite
Some project may use their own tool for building proto files like buf but still want to use CLI commands for serving, etc...
Describe the solution you'd like
Adding a flag, like for example --skip-proto, that skips the process of building protofiles and directly build the chain sources.
The flag would be proposed to the two commands running the build process
@robert-zaremba we implemented a caching layer so CLI won't generate code for every module each time there is a file change or when you run the chain build or generate commands.
But for CI purposes, as you suggested before, it makes sense to have a --skip-proto which could be useful in case cache files are not persistent on the CI.
Mentioning you for visibility, as this might be interesting for your use case.
Is your feature request related to a problem or issue you encountered? Please describe.
The current build process when serving a chain always building proto files with the embedded protoc of Ignite
Some project may use their own tool for building proto files like
buf
but still want to use CLI commands for serving, etc...Describe the solution you'd like
Adding a flag, like for example
--skip-proto
, that skips the process of building protofiles and directly build the chain sources.The flag would be proposed to the two commands running the build process
The text was updated successfully, but these errors were encountered: