-
Notifications
You must be signed in to change notification settings - Fork 334
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
Support Protobuf Imports #254
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain why the default (currentDirectory) was an issue and /
(root directory) works apparently? I'm unsure if I understand the actual circumstances causing the issue.
Without the removal of the "/" at the beginning of the filePath, the parser is failing. Error Log:
My guess the files are parsed twice, once via input "/test_b.proto" and once via import "test_b.proto" |
Co-authored-by: Martin Schneppenheim <weeco91@gmail.com>
Thanks for taking a look and finding this! |
Thanks for merging! :) |
Just FYI @CEikermann this broke protobuf support if the Git provider (instead of file provider) is used. Can you post what your protobuf configuration looked like, so that I can figure out a solution that works for both? |
Sorry this was not intended. #237 (comment) is this enough for you to reproduce? You can just use version 1.4 to reproduce this bug |
@CEikermann I just tested this locally and I was not able to reproduce this. It might be because I'm running on windows at the moment, but I could probably also test on Mac. I tend to revert your changes made here because of that. In my case an import like |
I just pushed a version that removes the prefix |
@weeco I have tested with master 11afdfa I do get an error when launching the kowl docker container
|
As addition to #237 (comment) docker-compose.yml
Docker Desktop 4.0.0 @ MacOS 11.4 You can not reproduce this on your env with the given files? |
@weeco are you able to reproduce the issue on your env? |
@CEikermann Yes, I can reproduce it using Docker, not within my IDE unfortunately. So I'm not entirely sure what's going on there, but I will try to figure it out as soon as I have some time for it |
Have created an follow up issue of this: #265 |
Fixes #237
Fixed by removing the "/" at the beginning of all file paths and added "/" as import path to the proto parser