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

I wanted to make the following recommendations on the AST node names for import specifiers:

• ImportDefault -> ImportDefaultSpecifier
• ImportStarAs -> ImportStarAsSpecifier (or ImportNamespaceSpecifier as babel calls it?)
• ImportSpecific -> ImportNamedSpecifier

The comments for these should also probably be updated (ex. on ImportDefault it should go from /// e.g. import

• 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

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)

I wanted links to open in a new tab and I found this blog:
https://sosuke.com/writing-custom-extensions-for-the-remarkable-javascript-markdown-parser/

but I noticed that the source code has a options.linkTarget option so I didn't have to use it:
https://github.com/jonschlinkert/remarkable/blob/dev/lib/rules.js

Please document all the options on the main page or put a link to a list of opti

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.

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 attempted to use a Vector config that included the new encoding table but it was on an older version of Vector. It produced the following configuration error:

[sinks.company_api_http]
type = "http"
inputs = ["company_api_rename"]
uri = "http://{{ consumer_instance.ec2_private_ip_address }}:{{ consumer_port }}"

[sinks.company_api_http.encoding]
except_fields = ["metadata.shar

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

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")

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

• Platform: Darwin C02XH15QJHD4 18.2.0 Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64 x86_64
• Mercury Parser Version: 2.1.0
• Node Version (if a Node bug): 11.5.0

Expected Behavior

Expect all headings within Medium articles to be present within parsed content.

Current Behavior

h tags are stripped from the cont

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

Your parser permits lazy evaluation of the ternary operator - ? - : -, and gosh does so:

~$ gosh
$ (( 1 + 1 == 2 ? 1 : $( echo foo >&2; echo 1) )) 
$  # bash would output foo here

This is great, but perhaps it should be optional or noted somewhere?

Source: http://mywiki.wooledge.org/BashFAQ/031#Theory.

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

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)

(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

Note: Similar to #899

Describe the bug

The LIMIT and OFFSET present at the end of a UNION query should be associated with the UNION query as a whole. Currently, it is being associated with the last SELECT query in the UNION.

To Reproduce

Steps to reproduce the behavior:

1. Example SQL

SELECT * FROM table1 UNION SELECT * FROM table2 ORDER BY col LIMIT 4 OFFSET 5