Issues on GitHub are intended to be related to bugs or feature requests, so we recommend using our other community resources instead of asking here.

• SOAR Doc
• Any other questions can be asked in the community

我通过程序把explain 语句的结果拼接到 soar -report-t

Issue type: feature

I found the https://github.com/arcticicestudio/nord-docs to be the best looking documentation site built with Gatsby.
It would be great to have it as a Gatsby Theme for reuse.

I am looking to enforce documentation on the interfaces and all of its properties using eslint. I have installed eslint-plugin-tsdoc package in my project. Is there a rule to enforce it?

Thanks

A few restrictions are supported for “holes” already.
A search for alphanumeric characters and punctuation can be specified by a syntax which is slightly different from other filter possibilities.

I imagine that advanced filters could be specified directly after the match identifier.

• Character class
• Regular expression
• Predefi

When using Babel syntax highlighting you have to disable the default JavaScript package in order for it to be used in HTML script tags, and other such places.

After disabling the default JavaScript package, instead of switching to using Babel after restart like other syntax highlighters, markdown highlighting breaks in the first js/`javascript

When commenting out multiple lines with line comments (cmd + /), empty lines in the selection will get comments and the space on those lines will affect the indent level of the comments. For example this...

![image](https://user-images.githubusercontent.com/1944277/65818238-bc9df000-e

I think the documentation could be slightly improved with gogrep-related materials, like https://github.com/mvdan/talks/blob/master/2018/gogrep.slide

It gives a pretty good introduction for people who are new to a concept of ast-based code matching.

That .slide can be compiled into PDF, uploaded to a speakerdeck and that speakerdeck link can be added to a README.

Does it make sense? :)

This might be more me than the theme, but I can not see the .env file at all in the tab. If there is a setting or an option to enable/disable that would be great. I was not able to find anything obvious.

I have File Colors disabled, and the related issues showed a fix when updated to 2019.1.3

![image](https://user-images.githubusercontent.com/31537/68088469-d7870400-fe1c-11e9-85dc-ca251b7

In sublime text, the string literal prefixes (e.g, the "f" in f'a string') and function arguments (names and values) are separate highlight groups:

It would be nice if we could have this in vim, too. :)

I can't run readme anymore after updating node from v8 to v10...

node: v10.14.1
npm: v6.4.1
OS: MacOS Sierra

A@anthony:~/git/someproject (master) $ readme
Markserv boot: starting Markserv...
path.js:39
throw new ERR_INVALID_ARG_TYPE('path', 'string', path);
^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type object
a

It's hard to understand what phpgrep does, how to use it and why it's useful.
Need to figure out how to fix that.
Suggestions are welcome.