Move message views/components to an add-on
Open
Nobody has claimed this yet.
Component-UI
enhancement
- Dominant language
- Java
- Stars
- 15.8k
- Forks
- 2.6k
- Avg merge
- 13h 16m
- Merged PRs (30d)
- 17
Description
The views and components that show the (e.g. HTTP) messages do not need to be in core and being in an add-on allows to enhance (or fix) them without the need to wait for a full release.
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 identifying the core views and components that display HTTP messages and the existing add-on boundary. Determine which dependencies must move with them; done means those views and components are provided by an add-on rather than core, allowing fixes or enhancements without waiting for a full release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100