resource: Improve parameter naming; support JSON encode #394
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The API documentation is inconsistent in the use of
resource_id. This change departs from the API docs and consistently uses:resource_id: ID of the linked to object, e.g. the Object Store IDid: ID of the "resource", e.g. the Resource (link) IDThe API docs will be updated accordingly.
Additionaly,
jsontags have been added to theResourcetype. This allows aResourceto be properly encoded as JSON.