matrix-org / matrix-org/complement
Test unit length compliance (255 bytes vs unicode points)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 99
- Forks
- 72
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 8
Description
This follows https://github.com/matrix-org/matrix-spec/issues/1001, I think it'd be good to add a test that essentially instigates this behaviour, trying out strings of emojis that are less than 255 codepoints, but are more than 255 bytes.
The only question left is how many of the different fields we're going to test, I'd suggest to at least check:
- `type`
- `state_key`
- `user_id`
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
No file or existing test path is named. Locate the Complement tests covering unit-length validation, then add coverage for emoji strings under 255 codepoints but over 255 bytes in at least type, state_key, and user_id. Done means the compliance test reliably exercises the byte-versus-codepoint behavior described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100