Regex properties in macros
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 132
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Right now, in a code returned from a macro, regex property notations like /regex/.text render as [native code]. ToDo fix. The current workaround is to use the (get /regex/ property) notation or chaining with (do /reg/ (.stuff)), the same can be used as an internal fix. (Alternatively, simply stop translating them into regexes when parsing, leave as strings.)
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 by reproducing a macro that returns a regex property such as /regex/.text, then compare its output with the documented (get /regex/ property) and (do /reg/ (.stuff)) workarounds. Trace the macro parsing or translation path and determine whether regex properties should preserve their property access; done means the returned code no longer renders the property as [native code].
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100