ocaml-dune / ocaml-dune/binary-distribution
Stop inlining assets into OCaml code
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 4
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
The code currently inlines the static assets that it uses into the binary. This is doubtlessly convenient for deployment but makes changes to them hard as every change has to pull the asset out, convert it from JSX syntax to e.g. SVG, do the change and inline again. This makes any change to the assets very tedious.
An alternative to save on this effort could be to use ppx_inline or similar solutions to inline the assets at build-time.
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
The issue names no files or tests. Start by locating the current static-asset inlining and build configuration, then evaluate ppx_inline or a similar build-time approach. Done means assets can be edited separately while still being embedded in the built binary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100