Clarify various usage scenarios for URI templates #387
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Format the one we have better, and also explain how using both instance data and describing client input is analogous to common interactive form usage.
handrews
requested review from
philsturgeon,
awwright,
jdesrosiers,
Relequestual and
dlax
|
Anyone? This is not a large PR, and does not change the spec behavior at all. |
dlax
approved these changes
Sep 7, 2017
Relequestual
approved these changes
Sep 7, 2017
gregsdennis
added
clarification
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Format the one we have better, and also explain how using
both instance data and describing client input is analogous
to common interactive form usage.
This is a response to #288, in that it is an attempt to explain
why these features work as they do. The discussion there
has not produced any alternative that solves the use case
added here (defining input conditions with schemas, but
allowing the existing data to remain unchanged if no
action is taken- identical to pre-populating HTML form
input widgets with "value").
If @jdesrosiers comes up with such a proposal, we will
definitely consider that. Otherwise, I am asking reviewers
to approve this if they feel that the given use cases justify
the current behavior.