Skip to content
#

parser

Here are 6,366 public repositories matching this topic...

postcss
StephenEsser
StephenEsser commented Oct 25, 2019

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
joshbruce
joshbruce commented Apr 13, 2020

miracles

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
zachelrath
zachelrath commented Jul 9, 2019

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
GuyLewin
GuyLewin commented Oct 15, 2019

Multiple different Javascript snippets can result in a LineComment node:

// type1
<!-- type2
--> type3

From current Esprima's output there's no way to know which one of these 'styles' was used as a comment.

Since this is specific to LineComment nodes, it's possible to split the type of node from 'LineComment' into 3 node types (one for each style). But I assume that wo

rbalet
rbalet commented Nov 19, 2019

🐛 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` |
vector
gabejohnson
gabejohnson commented Apr 10, 2017

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

nieksand
nieksand commented Jul 20, 2016

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
FlorianRappl
FlorianRappl commented Nov 16, 2016

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
mercury-parser
svenwiegand
svenwiegand commented Aug 28, 2019
  • 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
alexanderdickson
alexanderdickson commented Nov 25, 2019

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

tsdoc
raphinesse
raphinesse commented Feb 12, 2020

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

Sammyalhashe
Sammyalhashe commented May 1, 2020

Correct me if I'm wrong, but isn't it not correct that you pass globals as the surrounding environment in LoxFunction's call (https://www.craftinginterpreters.com/functions.html#function-objects)? If I understand this correctly, globals holds a fixed reference to the outer global environment, and it doesn't appear to change. Maybe I missed something, but when you define a recursive call, like yo

picocli
deining
deining commented Dec 1, 2019

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

doc

Improve this page

Add a description, image, and links to the parser topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the parser topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.