Skip to content
New issue

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

Use common Markdown for descriptions #290

Merged
merged 2 commits into from
Apr 6, 2017
Merged

Use common Markdown for descriptions #290

merged 2 commits into from
Apr 6, 2017

Conversation

RomanHotsiy
Copy link
Contributor

@RomanHotsiy RomanHotsiy commented Mar 28, 2017

There are a lot of different Markdown dialects. Let's stick to Common Markdown as it was recently done by GitHub and others.
I believe most of markdown renderers will support soon or already support Common Markdown.

Copy link
Contributor

@wincent wincent left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @RomanGotsiy. Makes sense to me, but I'll leave this open for a while to give others a chance to chime in.

@@ -74,9 +74,9 @@ underscores.

All types in the introspection system provide a `description` field of type
`String` to allow type designers to publish documentation in addition to
capabilities. A GraphQL server may return the `description` field using Markdown
capabilities. A GraphQL server may return the `description` field using [Common Markdown](http://spec.commonmark.org/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like this long line would best be wrapped.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@wincent
Copy link
Contributor

wincent commented Mar 28, 2017

And for reference, I looked up this GitHub blog post on the subject of the Markdown spec.

@wincent
Copy link
Contributor

wincent commented Apr 6, 2017

Ok, going to apply a couple of tweaks and merge this (namely, that the spec is called "CommonMark" and doesn't refer to "Common Markdown"). Thanks!

- Link to http://commonmark.org/ rather than http://spec.commonmark.org/ as it provides a more user-friendly landing point.
- "Common Markdown" → "CommonMark"
- Backticks around "description".
@wincent wincent merged commit c510a64 into graphql:master Apr 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants