-
Notifications
You must be signed in to change notification settings - Fork 17
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
dogma returns error invalid json when called dogma cat --jsonpath #36
Comments
Thanks for the report. Let me take a look it soon. |
I capturing response body that come from centraldogma service (run via docker):
The content return Is it bug on centraldogma service? |
I read test code from https://github.com/line/centraldogma/blob/master/server/src/test/java/com/linecorp/centraldogma/server/internal/api/ContentServiceV1Test.java#L276. Looks like it's intention. |
@minwoox Is it possible that ref: https://github.com/line/centraldogma-go/blob/master/content_service.go#L88 |
@wingyplus Sorry about the late response. Was on a business trip and couldn't take care of this issue. |
@minwoox Sorry for disturbing you. I see it using inside LINE Man Team (but another team not my team). And I interesting to use it in my personal project. :) |
@wingyplus Ah that's cool! If you want to talk directly, you can use the company slack #help_centraldogma. :-) |
@minwoox Thanks for your guide. :D |
Motivation: Currently, we indent JSON content if the `EntryType` is `JSON`. However, the content can be just a string when we use JSON path. Modification: - Do not indent when the content is not JSON object Result: - Fix line#36 - You no longer see parsing error when fetching JSON content using JSON path
Motivation: Currently, we indent JSON content if the `EntryType` is `JSON`. However, the content can be just a string when we use JSON path. Modification: - Do not indent when the content is not JSON object Result: - Fix #36 - You no longer see parsing error when fetching JSON content using JSON path
These steps below I copied from tutorial.
Reproduce steps:
start centraldogma with docker command:
Then running with following steps:
Expected result:
The
./dogma -c http://localhost:36462 cat --jsonpath '$.a'
in the last step should returns"b"
as mentioned in tutorial website.Actual Result
Dogma version:
And found it in current master branch.
The text was updated successfully, but these errors were encountered: