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
{{ message }}
This repository has been archived by the owner on Mar 4, 2022. It is now read-only.
This is quite biased as the import path is fixed here. Usually I have to generate it for the server app and client app which are different (and currently non-standardised). So I keep another copy of this with a different import_path.
I wanted to use prototool generate to generate for both the configs that are in YAML. However, when I run
prototool generate service_definition.proto --config-data "protoc: version: 3.8.0 lint: group: uber2 generate: go_options: import_path: my-app/src/api/grpc plugins: - name: gogofaster type: gogo flags: plugins=grpc output: generated_model"
invalid character 'p' looking for beginning of value
This suggests that it is unable to parse YAML.
I checked #224 and noticed that the test cases also have JSON config as test data, so I'm guessing there's a gap here in what the expectations are and what the outcome is. I could not understand the code much, and am on a time crunch, so any insights on a workaround, or an acknowledgment that this is a bug, would be appreciated.
Thanks!
The text was updated successfully, but these errors were encountered:
I have a YAML like this:
This is quite biased as the import path is fixed here. Usually I have to generate it for the server app and client app which are different (and currently non-standardised). So I keep another copy of this with a different
import_path
.I wanted to use
prototool generate
to generate for both the configs that are in YAML. However, when I runi get the following error
This suggests that it is unable to parse YAML.
I checked #224 and noticed that the test cases also have JSON config as test data, so I'm guessing there's a gap here in what the expectations are and what the outcome is. I could not understand the code much, and am on a time crunch, so any insights on a workaround, or an acknowledgment that this is a bug, would be appreciated.
Thanks!
The text was updated successfully, but these errors were encountered: