Refmting multi-line ppx strings
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
Actual:
let compose:
_ => unit
[@@ocaml.deprecated
{|
Use the |> as an infix operator to chain the
result of one function into another:
`compose(f, g, h)(x)`
in JS goes to
`x |> h |> g |> f`
in Reason.
|}
];
Expected:
let compose: _ => unit [@@ocaml.deprecated {|
Use the |> as an infix operator to chain the
result of one function into another:
`compose(f, g, h)(x)`
in JS goes to
`x |> h |> g |> f`
in Reason.
|}];
Or if the first line was really long:
let compose:
oneThing =>
anotherThing =>
oneMore =>
unit
[@@ocaml.deprecated {|
Use the |> as an infix operator to chain the
result of one function into another:
`compose(f, g, h)(x)`
in JS goes to
`x |> h |> g |> f`
in Reason.
|}];
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 the formatting examples in the issue and locating the formatter entry point that handles PPX attributes and multi-line strings. Done means the formatter keeps the attribute on the appropriate line while preserving the string contents and produces the expected output for both examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100