-
when the tree choice is "parser error", and then I fix the error, that choice becomes unavailable. So "parsed" is selected and the parse tree displayed. which is fine
but that selection change doesn'…
-
### arrow-parens
- [`app/components/codeSubmission/codeDisplay.tsx:27`](https://github.com/atomist/microgrammar-explorer/blob/98f4a9e74910ba5eac266da4fcdd43b981d46c02/app/components/codeSubmission/co…
-
### lodash:
-
### arrow-parens
- [`app/components/codeSubmission/codeDisplay.tsx:27`](https://github.com/atomist/microgrammar-explorer/blob/d23632a786d62880f7cab1c377a6e21d6f347820/app/components/codeSubmission/co…
-
### lodash:
-
### lodash:
-
### arrow-parens
- [`app/components/codeSubmission/codeDisplay.tsx:27`](https://github.com/atomist/microgrammar-explorer/blob/d0112184787290f0eb574336b2bb491743f4a1a2/app/components/codeSubmission/co…
-
Error messages still leave a lot to be desired. Try to be as informative as possible, showing the point within the input input where the failure occurred.
-
A microgrammar phrase like "key = ${value}" (with no term definitions) is not sufficiently specified.
This should throw an exception on construction or something, because we don't know what express…
-
### deprecation
- [`test/integration/ParseOwnTerms.test.ts:39`](https://github.com/atomist/microgrammar/blob/8066f611c508021d154878f3f818d694eacb33d8/test/integration/ParseOwnTerms.test.ts#L39): _(er…