For some reason name, params and raws properties are not displayed in AtRule documentation (http://api.postcss.org/AtRule.html) though they are presented in JSDoc.

Marked version: 0.7.0

• December 2017: Should we perform a miracle?
• February 2018: MarkedJS Organization is opened. Core team and roadmap established.

This is a community effort. The core team is primarily here for c

There should be documentation for the $Block & $Line variabels and $Block['element'] and what the diffrent input are used for, e.g Type or Name

• the leaf level should report the error context clearly, without appending context from the levels above
• add config to allow panic on error to fail fast

Code Line: https://github.com/swc-project/swc/blob/master/ecmascript/parser/src/lexer/jsx.rs#L60

@kdy1

Full HTML escape characters support: LuoZijun/es@b67338f

Ref: HTML Character entity references

benchmark:

test lexer::htmlentity::bench_escape_html_with_bytes   ... ben

A link in Chapter 2 of the docs points to Chapter 2 rather than Chapter 3, as intended.

Search for "Chapter 3. Lexical Analysis (Tokenization)" on this page: https://esprima.readthedocs.io/en/latest/syntactic-analysis.html

PR incoming 👍

Thank you for providing Remarkable.

I'd like to write plugins but the available documentation is more of an internal documentation.

I am also unsure whether every plugin is simply applied in a row during runtime - and then the plugin decides whether to process the input or not? As this means a plugin is not explicitly registered with a MARKDOWN-TAG like:

`.addPlugin('MARKDOWN-TAG', isInl

I'm opening this issue as more of a reminder than a one-time task.

It took me > 6 months to get familiar with the code base and I'm still weak in areas. Now this may say more about me than it does about the project, but I suspect the latter.

Adding header comments outlining the purpose of a file/class and how it's used by its dependents could go a long way toward easing onboarding for new co

i tried to add this lines in
https://github.com/globalizejs/globalize/blob/master/examples/app-npm-webpack/app/index.js#L1

Globalize.load( require( "cldr-data" ).entireSupplemental() );
Globalize.load( require( "cldr-data" ).entireMainFor( "en", "es" ) );

got a lot of warnings
and error

ERROR in ./~/cldr-data/index.js
Module not found: Error: Cannot resolve module 'fs' in 

The documentation here incorrectly states, "This will mangle all properties that start with an underscore." when in fact the provided example will mangle all properties that END with an underscore.

I notice that there's a broken links on https://docs.rs/nom/3.2.1/nom/ for example:

1. the design of nom
2. working in parser

etc.
I'd gladly to help with improving the docs, as long as I know where is the repository for this website. Thanks in

This keeps the naming for key names consistent. Ex: the host_key option on the file and socket sources.

I'm using AngleSharp version 0.13.0 with Dot Net Core 3.0.
I'm trying to Connecting JavaScript Evaluation like this document.

But the WithJavaScript() could not found anymore.
How can I fix that?
Image
Thank you

Update 1: Okay, I fixed t

Example in ReadMe is incorrect,

// Or use can access fields by index!
jsonparser.GetInt("person", "avatars", "[0]", "url")

Should be,

// Or use can access fields by index!
jsonparser.Get(data, "person", "avatars", "[0]", "url")

Hello, by default, the new field is written to the end of the class, the code writing specifications are not friendly. Is there a similar layout API? For example, the class is divided into two parts, the upper part is the field area, and the lower part is the function area. All fields are added to the end of the field area, and the function is the same

Typing print() in the jscodeshift transformer triggers browser print dialog

To Reproduce
Steps to reproduce the behavior:

1. Specify to use jscodeshift
2. Type print() in bottom left corner
3. See the bug

Expected behavior
Shouldn't do that

Browser (please complete the following information):

• OS: OS X
• Browser Chrome
• Version 78.0.3904.108

**astexplorer

For example, ParamExp has a Name field of type *Lit, but it can never be nil. The reason it's a pointer is for consistency with all the other literal fields.

In the documentation, this example is given for Lexing with Moo:

@{%
const moo = require("moo");

const lexer = moo.compile({
  ws:     /[ \t]+/,
  number: /[0-9]+/,
  word: /[a-z]+/,
  times:  /\*|x/
});
%}

# Pass your lexer object using the @lexer option:
@lexer lexer

# Use %token to match any token of that type instead of "token":
multiplication -> %number %ws %

@pgonzal and I were talking in an email thread about parsing params in api-extractor/tsdoc, and suggested I log an issue here to track the param parsing concerns.

Goals for param parsing should be;

1. Public exported classes/functions have correct jsdoc comments describing the thing.
2. If param comments are missing, api-extractor catches them and throws an error.
3. If params are out of o

I don't see a link in the README.md that lets people get to the docs that cover the API for this package... can that be added?

Example:

posthtml()
    .use((tree) => {
        tree.walk((node) => {
            console.log('node', node);
        });
    })
    .process(html, { sync: true })
    .html;

Output:

node <!DOCTYPE html>
node 

node { tag: 'html',
  attrs: { lang: 'ru' },
  content:
   [ '\n',
     { tag: 'meta', attrs: [Object] },
     '\n',
     { tag: 'head', content: [Array]

Bug 1

I reported a similar issue with the CHANGE keyword. We have a legacy app that uses the Mysql keyword "DISABLE" as a column name. Since it's legacy, we can't easily change the column name, and it is causing the sql parser to break.

To Reproduce
Steps to reproduce the behavior:
2. Parsing "INSERT INTO SOMESCHEMA.TEST (DISABLE, TESTCOLUMN) VALUES(1, 1)" SQL using JSqlParser throws Js

I recently came across a simple, step-by-step tutorial for the Vaughan Pratt Parser.

Interested readers should go to https://engineering.desmos.com/articles/pratt-parser/ to read this tutorial. Should there be a problem with the link, search for "How Desmos uses Pratt Parsers".