feat(codegen): add file path for code generation errs #1357
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
related to invalid .proto files. instead of just returning with the parsing error, path info for the related file also included. e.g.: ``` file: /home/ilker/Documents/code/src/github.com/tendermint/starport/local_test/mov/proto/mov/tx.proto: <input>:17:1: found "}" but expected [field =] ```
Pantani
approved these changes
Jul 12, 2021
Jchicode
pushed a commit
to Jchicode/cli
that referenced
this pull request
Aug 9, 2023
related to invalid .proto files. instead of just returning with the parsing error, path info for the related file also included. e.g.: ``` file: /home/ilker/Documents/code/src/github.com/tendermint/starport/local_test/mov/proto/mov/tx.proto: <input>:17:1: found "}" but expected [field =] ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
related to invalid .proto files.
instead of just returning with the parsing error, path info for the
related file also included. e.g.:
related to #1342.