Placement of closing `>` in JSX
Open
Nobody has claimed this yet.
KIND: FEATURE REQUEST
Printer
- Dominant language
- OCaml
- Stars
- 10.3k
- Forks
- 438
- PR merge metrics
- No merged PRs in 30d
Description
/* Now */
<Component
prop1
prop2>
("child" |> ReasonReact.stringToElement)
</Component>
/* VS */
<Component
prop1
prop2
>
("child" |> ReasonReact.stringToElement)
</Component>
I used to the latter, imo it's easier to spot this place this way. Also, it's consistent with:
<Component
prop1
prop2
/>
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 locating the JSX formatting or parsing entry point in the Reason codebase and compare the current output with the proposed layout. Confirm how self-closing JSX tags are formatted, then add coverage for the closing > placement and verify the formatter produces the requested style.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, ocaml
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100