oxidecomputer / oxidecomputer/hubris
Build fails if task is named using emoji
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
Currently there are a couple of places in the codebase that require task names to be valid identifiers. That's kind of arbitrary, really, and prevents naming tasks using emoji.
We could fix this by detecting non-identifier task names and lowering them to valid identifiers, e.g. by replacing unsupported codepoints with hex equivalents.
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 locating the code paths that require task names to be valid identifiers and trace how task names are processed during the build. Determine how unsupported codepoints should be lowered to valid identifiers, then add coverage for emoji-named tasks and verify that the build succeeds without identifier collisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100