microsoft / microsoft/monaco-editor
[Bug] unreadable regular expression error
Open
Nobody has claimed this yet.
bug
confirmed
- Dominant language
- JavaScript
- Stars
- 46.8k
- Forks
- 4.1k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 1
Description
Reproducible in vscode.dev or in VS Code Desktop?
- Not reproducible in vscode.dev or VS Code Desktop
Reproducible in the monaco editor playground?
- Not reproducible in the monaco editor playground
Monaco Editor Playground Link
Monaco Editor Playground Code
text for regular expression `some(1.*`
Reproduction Steps
- open find and replace tab
- on mode "use regular expression"
- past value
some(1.*in find field
Actual (Problematic) Behavior
Expected Behavior
How in VS Code Desktop:
Additional Context
No response
Contributor guide
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 in the find and replace tab of the Monaco Editor Playground and reproduce the invalid expression some(1.* with regular-expression mode enabled. Compare the displayed error with VS Code Desktop; done means the invalid regular expression produces a readable error like the expected behavior shown in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100