Tools Module - Re: 3.2.1 messageimportance
Open
Nobody has claimed this yet.
3) tools module
- Dominant language
- JavaScript
- Stars
- 53
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Would not "importance" be a higher level requirement than just for messages? For example, in a scenario where a page is being "simplified", wouldn't the author want to denote sections of the content that is "critical" (and so do not "simplify it" away)?
Could we not just reduce this to a value of "importance" and let it cover more use-cases?
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 with Tools Module section 3.2.1 and the definition of “messageimportance.” Compare its message-only scope with the proposed broader “importance” concept, then clarify the intended use cases and acceptance criteria. Done means the specification has a clear, resolved decision on the term and scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100