[BUG] Invalid identifier allowed as record field name
@JordanBoltonMN is already working on this.
Since Jul 20, 2021.
Assessment
This issue has not been assessed yet.
Description
Expected behavior
To align with Query Editor's behavior, in [1.=true], "1." should be rejected as an invalid identifier.

Actual behavior
The parser (as tested in VSCode using the Power Query / M Language extension) accepts the above as valid M.
Additional context
https://github.com/MicrosoftDocs/powerquery-docs/issues/30 discusses the grammar for a generalized identifier.
- Dominant language
- TypeScript
- Stars
- 137
- Forks
- 34
- Avg merge
- 50m
- Merged PRs (30d)
- 1
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.
More from microsoft/powerquery-parser
-
enhancement
microsoft/powerquery-parser#399 · 1 assignee ·
-
bug
microsoft/powerquery-parser#370 · 1 assignee ·
-
bug
microsoft/powerquery-parser#355 · 1 comment · 1 reaction · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
microsoft/powerquery-parser#354 ·
-
bug
microsoft/powerquery-parser#340 · 4 comments · 1 assignee ·
All issues in microsoft/powerquery-parser
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·