question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support Inline Markdown Documentation

See original GitHub issue

Version and Environment Details

Operation system: macOS High Sierra 10.13.5

IDE name and version: WebStorm 2018.2.5

Plugin version: 1.7.2

Expected Behaviour

Inline markdown comments with double quotes (single-line) and triple double quotes (multi-line) which apollo-server at least supports as a means of documenting the scheme are syntax highlighted and maybe interpreted by the plugin.

Actual Behaviour

Inline markdown comments are considered an error:

Error:(5, 3) Syntax Error GraphQL (5:3) Unexpected String

Screenshot of error: Error:(5, 3) Syntax Error GraphQL (5:3) Unexpected String

And syntax highlighted as errors:

Screenshot of syntax highlighted

Steps to Reproduce / Link to Repo with Reproduction and Instructions

  1. Create a JS file in an apollo-server project
  2. Import the gql template template tag from apollo-server
  3. Create a template literal, tag it with gql, and fill it with a valid GraphQL type using the standard GraphQL Schema Language
  4. Add a single- or multi-line comment to the type per the documentation here.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:3
  • Comments:9

github_iconTop GitHub Comments

2reactions
jimkyndemeyercommented, Nov 9, 2018

Hi Brandon.

Thanks for using the plugin.

Documentation in quotes/tripe quotes was a breaking language change that was added to the GraphQL spec after the V1.x parser and language service for this plugin was built. V1 expects documentation to be in # line comments above types and fields.

V2 of this plugin follows that newer language spec, but is still work in progress. Currently V2 shows documentation in completions, but the quick documentation viewer found in V1 is yet to be built.

You can read more about V2 in #164 and https://github.com/jimkyndemeyer/js-graphql-intellij-plugin/releases and try it out if you prefer to use quotes for the documentation.

I’ll keep this issue around as markdown support would be a nice addition to V2.

Best regards, Jim.

1reaction
jimkyndemeyercommented, Mar 10, 2019

Closing this as markdown documentation has been supported since 2.0.0-alpha-4.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Markdown Syntax Documentation - Daring Fireball
Markdown supports two style of links: inline and reference. In both styles, the link text is delimited by [square brackets]. To create an...
Read more >
Basic Syntax - Markdown Guide
Nearly all Markdown applications support the basic syntax outlined in the original Markdown design document. There are minor variations and discrepancies ...
Read more >
Markdown Cheatsheet · adam-p/markdown-here Wiki - GitHub
Markdown Here supports highlighting for dozens of languages (and not-really-languages, like diffs and HTTP headers); to see the complete list, ...
Read more >
Introductory Guide to Markdown for Documentation Writers
Markdown editor with live preview make your Knowledgebase intuitive and lightweight for technical writers. Keep distractions away and focus ...
Read more >
How to use Markdown for writing technical documentation
As we are storing Adobe Docs content in GitHub, it can use a version of ... Markdown supports the placement of code blocks...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found