docs: clarify trailing slashes in Device controls #78
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
andrewbonney
force-pushed
the
trailing-slash
branch
from
f2a4853
to
89abbdf
Compare
andrewbonney
force-pushed
the
trailing-slash
branch
from
89abbdf
to
a559beb
Compare
garethsb
approved these changes
Jun 12, 2019
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.
Resolves #65
Given the number of implementations which will now exist with a trailing slash present in the 'href' I've stopped short of mandating that the (preferred) non-trailing slash version is listed. Instead this adds recommendations for clients in the consistent handling of 'href' attributes.