Issue

When using postcss v7.0.20 the webpack compilation fails with the following stack trace.

✖ ｢wdm｣: TypeError: Cannot read property 'value' of undefined
    at /Users/username/workspaces/terra/terra-core/9.css:220:3
    at new Quoted (/Users/username/workspaces/terra/terra-core/node_modules/postcss-values-parser/lib/nodes/Quoted.js:19:28)
    at cloneNode (/Users/username/works

Please see previous #1522 for backstory.

December 1st, 2017 the core team came together to take on Marked. Since then a lot has happened...a lot. Some changes in direction we wanted to talk about:

1. Spec-compliance, semver, and a 1.0 release
2. Make Marked more extensible ra

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

Are there any plans to submit SWC to the Kangax compatibility table. This is my (and I think most web developer's) goto resource when trying to determine which ES features a given project supports. It includes all common web browsers, as well as babel and typescript. I believe it also comes with a test suite.

https://kangax.github.io/compat-table/es6/ (+ the next version).

I would love to us

Currently, when SortMapKeys is set to true in Config, map keys are sorted using a standard alphanumeric sort. It should be possible to specify a custom map key sorting function to use, in order to prioritize certain map keys over others.

Example: Standard SortMapKeys behavior:

cfg := jsoniter.Config{
   SortMapKeys: true,
}.Froze()

m := map[string]int{
   "beta": 2,
   "alp

The ForInStatement and ForOfStatement interfaces can also have VariableDeclaration as the value for the left property, as specified by the spec at https://www.ecma-international.org/ecma-262/10.0/index.html#sec-for-in-and-for-of-statements and demonstrated by running the following code:

esprima.parseScript('for (const a in b) {}');
esprima.parseScript('for (const a of b)

🐛 Bug Report

when using backtick within a table, the pipe | wont be espace by the backslash \
(originally raised here)

To Reproduce

try this code within a docusaurus md file

| Test                            | x        | x   |
| ------------------------------- | -------- | --- |
| `this pipe \| should be espace` |

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'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

According to the CLDR documentation, we can specify a region overriding the region specified in the language identifier.

Does Globalize support this extension?

If yes, any help would be greatly appreciated.

Azure Event Hubs is like a managed Kafka service:

Allow existing Apache Kafka clients and applications to talk to Event Hubs without any code changes—you get a managed Kafka experience without having to manage your own clusters.

This suggests that we could wrap the existing kafka sink. I'd prefer that we wrap it since it is techni

https://docs.rs/nom/5.0.1/nom/macro.tag_bits.html documentation says that tag_bits signature is tag_bits!(type, count, pattern). The first parameter, type, was removed in the commit 0313c1d63fe5fd074989c958073f2340385a1d43, but documentation was not updated.

take_bits! documentation has a similar issue.

I'm dealing with a large, flat json payload that has 100+ keys in a map.

I hit panics when using EachKey with the full list of json keys:

goroutine 1 [running]:
panic(0x4e8ac0, 0xc42000a0f0)
    /home/niek/go17/src/runtime/panic.go:500 +0x1a1
github.com/buger/jsonparser.EachKey(0xc421480000, 0x11ac, 0x11ac, 0xc420050e30, 0xc4200da000, 0xaf, 0x100, 0x0)
    /home/niek/workspace/src/github.c

The v1 release is coming closing (as is the v0.10; the last milestone before v1), which means a full documentation will be required.

This has a lot of impact:

• Move parts of the Wiki to the docs
• Create a common documentation infrastructure (common means: good for all AngleSharp projects)
  • Format of the documentation (potentially markdown with many extensions)
  • Special diagram lan

My presumption is that there should be a way to do this automatically as part of the release process.

I'm not 100% how best to achieve this, so before running with it I'd like to open it out for discussion.

To start things off, this SO question has a few answers/suggestions.

One suggestio

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

• Platform: MacOS
• Mercury Parser Version: master
• Node Version (if a Node bug): v11.1.0
• Browser Version (if a browser bug): n/a

Description

I have created a custom extractor for https://www.gruene.de/themen/arbeit which delivers the expected results for content and lead_image_url with the following specifications:

export const WwwGrueneDeExt

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.

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

The docs say:

Macros are expanded at compile time and inserted in places they are used

Now consider this grammar:

id[el]		-> $el		{% id %}

plain_test	-> word		{% id %}
macro_test	-> id[word]	{% id %}

word		-> [\w]:+	{% d => d[0].join("") %}

Given above documentation and grammar I would have expected that macro_test w

(at 3dc7cc2)

default-jdk on Ubuntu 18.04 installs openjdk-11-jdk; when I use it to compile jlox and run the tests, I get the following:

roger@rlipscombe:~/Source/munificent/craftinginterpreters [master] $ ./util/test.py jlox
FAIL: test/number/nan_equality.lox
      Expected output "false" on line 7 and got "true".
      Expected output "true" on line 8 and got "false".

238 tes

Describe the bug
SQL Server supports assigning a value to a variable from a selected expression.
For example:

DECLARE @var INT;
CREATE TABLE tableName (id INT);

SELECT @var = 1;
SELECT @var = id FROM tableName;

To Reproduce
assertSqlCanBeParsedAndDeparsed("SELECT @var = 1");

System

• SQL Server 2017
• JSqlParser 3.1

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?

will be good to add example with async/await

Originally posted by @Grawl in posthtml/posthtml#115 (comment)

While answering #878, I realized, that both user manual and quick guide could be improved. Goal should be to get first time users started as quickly as possible.
Thinking back to my first time contact with picocli I remembered it wasn't straightforward for me to get things up and running, either. Don't get me wrong: The picocli manual is very complete, concise and was/is of great help for me in m