-
-
Notifications
You must be signed in to change notification settings - Fork 6
Pass include_paths via CLI? #70
New issue
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
Comments
Correct, we don't have a way to pass include paths from command line. In terms of cli I plan to add more CLI argument support with clap in next release. |
Thanks for the quick reply! I look forward to that new release. I am currently using vscode and more specifically, the following extension: https://github.com/ianandhum/vscode-protobuf-support Unfortunately, it marks all import statements as errors (red squiggles) in the |
Although, I have created a PR to address this issue. I wonder why you can't just create a |
Great question. I tried putting the toml file in my repo as well as a sibling of my |
A new release 0.11.5 with this has been published on crates.io |
Sorry, I'm not familiar with rust, but I have been trying to go through the code and as far as I can tell, there appears to be no way to pass the
include_paths
config option via a command line argument. Is that true? Thus far all I can see is that it's possible to set this value via the toml file:https://github.com/coder3101/protols?tab=readme-ov-file#%EF%B8%8F-configuration
Is it possible to do something like
protols --include_paths=/foo
? Am I just missing something obvious?The text was updated successfully, but these errors were encountered: