We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
I have the following file structure for proto files /VENDOR/MICROSERVICE/MODULE/VERSION/*.proto
/VENDOR/MICROSERVICE/MODULE/VERSION/*.proto
Here is a list of proto files for CRUDL
entity.proto create.proto update.proto delete.proto list.proto get.proto service.proto
And as a result, I'd love to have a barrel or something similar assembled to have a single import point.
I'm utilizing NestJS as a framework for microservice so there is *_PACKAGE_NAME generated in each file. As a result, barrel fails cause of conflicts.
*_PACKAGE_NAME
So the question is - by any chance is it possible to get *_PACKAGE_NAME only inside the file service is defined?
If not and it looks like it's not, do you think it's a good idea to add? Or probably just add barrel generation from within the ts-proto?
The text was updated successfully, but these errors were encountered:
Hi @arustamyansv , yeah that makes sense, we have an existing issue #212 that tracks this ask, but haven't had anyone put together a PR yet. Thanks!
Sorry, something went wrong.
No branches or pull requests
Hello,
I have the following file structure for proto files
/VENDOR/MICROSERVICE/MODULE/VERSION/*.proto
Here is a list of proto files for CRUDL
And as a result, I'd love to have a barrel or something similar assembled to have a single import point.
I'm utilizing NestJS as a framework for microservice so there is
*_PACKAGE_NAME
generated in each file.As a result, barrel fails cause of conflicts.
So the question is - by any chance is it possible to get
*_PACKAGE_NAME
only inside the file service is defined?If not and it looks like it's not, do you think it's a good idea to add?
Or probably just add barrel generation from within the ts-proto?
The text was updated successfully, but these errors were encountered: