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
Frontend developers are used to JSON structures, this is also what is expected in an API response for most JS frameworks these days.
Same as the YAML implementation, but configuration with JSON
Sometimes it's easier to reason about a simple endpoint returning a desired JSON structure where a full randomized CRUD scenario isn't really needed.
go version go1.8 darwin/amd64
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Feature Request
Frontend developers are used to JSON structures, this is also what is expected in an API response for most JS frameworks these days.
What is the expected behavior?
Same as the YAML implementation, but configuration with JSON
What is the motivation / use case for changing the behavior?
Sometimes it's easier to reason about a simple endpoint returning a desired JSON structure where a full randomized CRUD scenario isn't really needed.
Which version of golang, and which browser and OS does this issue affect?
go version go1.8 darwin/amd64
The text was updated successfully, but these errors were encountered: