electro-grammar
electro-grammar copied to clipboard
kitspace
:zap: A parser for electronic component descriptions
Bumps [tar](https://github.com/npm/node-tar) from 2.2.1 to 2.2.2. Commits 523c5c7 2.2.2 7ecef07 Bump fstream to fix hardlink overwriting vulnerability 9fc84b9 Use {} for hardlink tracking instead of [] 15e59f1 Only track previously...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Resolves: https://github.com/kitspace/electro-grammar/issues/18 Untested :)
Hello Kaspar, One thing that might be nice is the ability to collect the extraneous tokens, so that if user enters `100nF 0603 50V Kemet`, the `Kemet` token could be...
Is v2 already in point of test? I want to run it in Python to integrate in other tool. Should be interesting be available on PyPI. Also, as a KiCad...
0.1uF versus 0,1uF. I know in Germany people will write 0,1uF The problem comes down to queries like: 0,1uf 10% 0402 50v x7r vs 0.01uf, 50v, cog, 5%, 0603 Also,...
The CLI runner is slow, if we move the test-cases to JSON5, TOML or something similar we should be able to write a faster Python test-runner.
Antlr seems to have some support for cross-language actions embedded within Grammars, though I can only find one [reference to them](https://github.com/antlr/antlr4/blob/master/doc/antlr-project-testing.md#cross-language-actions-embedded-within-grammars) an it's in the context of testing Antlr itself....
I think this would ease #8 and of course it's been on the todo for the Antlr port from the start.
I think the parser output should be: ## Strict ```typescript { result: Result; warnings: Array; } // or { error: Error; } ``` ## Lax ```typescript { result: Result; ignored:...
@dvc94ch I noticed that you are adding MPNs for semi-conductors into the grammar itself. I am wondering: is this the best place for them? It might work well for really...