Should spaces between AO names and arguments be allowed?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 245
- Forks
- 80
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 2
Description
From https://github.com/tc39/proposal-temporal/pull/2574/files#r1235598629, I was surprised that ecmarkup didn't complain about there being a space between the name of an AO and its argument list.
Example: the following spec text didn't cause ecmarkup errors.
1. Set _item_ to ? ToPrimitive (_item_, ~string~).
I wasn't sure if this was another one of those cases of "whitespace is handled by the formatter" like https://github.com/tc39/ecmarkup/issues/536, but the build job complains about some whitespace issues (e.g. trailing spaces at end of line) so I figured I'd file this issue just in case this was the kind of whitespace issue that the build job should be worrying about.
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 by reproducing the example spec text in ecmarkup and compare its handling with the build job's existing whitespace checks. Determine whether a space between an abstract-operation name and its argument list should be accepted or reported, then add coverage for the chosen behavior and verify the build result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100