matrix-org / matrix-org/matrix-spec
Why do we put event types in the URL when sending messages? (SPEC-339)
Open
Nobody has claimed this yet.
A-Client-Server
wart
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Submitted by @matthew:matrix.org
It seems redundant data and doesn't buy us anything. I don't see how it's 'RESTy'. It does make it easier to filter for URLs in the Chrome network panel, but that's a pretty minor win
(Imported from https://matrix.org/jira/browse/SPEC-339)
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, test, or entry point is named. Start by reviewing the specification text that defines message URLs and event types, then determine whether the URL behavior should remain or change and record the decision in the spec.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100