Document content[html] for form requests
#3
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
There are a number of Micropub clients that support this form-based syntax, therefore we should make sure that this is document on the specification for anyone implementing it.
As I know GitHub folks would like it to be correctly cased!
jamietanna
changed the title
content[html] for form requests
|
Is there discussion for this anywhere? It seems like a big change from the current spec, which is pretty clear that if you want more advanced options like HTML, you need to use JSON. |
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.
There are a number of Micropub clients that support this form-based
syntax, therefore we should make sure that this is document on the
specification for anyone implementing it.
Duplicate of w3c#123, but for the new repo.