microsoft / microsoft/powerquery-parser
field-specification Deviation Double-Check
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 137
- Forks
- 34
- Avg merge
- 50m
- Merged PRs (30d)
- 1
Description
Hello,
In https://github.com/microsoft/powerquery-parser/blob/master/specification.md, the following deviation from the M language spec is mentioned:
- The field-specification construct requires an identifier. Instead identifer is replaced with generalized-identifier.
The spec currently contains the following grammar definitions:
field-specification:
optional(opt) field-name field-type-specification(opt)
field-name:
generalized-identifier
quoted-identifier
With the way field-name currently is defined, is the above-quoted bullet a legacy relic that can be removed?
Ben
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with specification.md and compare the quoted field-specification and field-name grammar with the referenced M language specification. Confirm whether generalized-identifier is already fully covered by field-name, then remove or retain the deviation note accordingly. Done means the specification accurately describes the language without a redundant legacy exception.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100