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
create by necessity can't have a path in the request, at least not a required one: that would deviate in the case of server-generated fields.
In general apply is a simpler for that reason.
My idea would be to have path in the request, and the path in the resource always be output-only.
But I'll file a ticket on this.
Originally posted by @toumorokoshi in #115 (comment)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In general apply is a simpler for that reason.
My idea would be to have path in the request, and the path in the resource always be output-only.
But I'll file a ticket on this.
Originally posted by @toumorokoshi in #115 (comment)
The text was updated successfully, but these errors were encountered: