MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers
[Version History] Collision with MiniApp Manifest version field
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.4k
- Forks
- 286
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 8
Description
Potential issue for the version history explainer: https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/VersionHistory/explainer.md
The MiniApp Manifest is an extension to the web app manifest, and it already defines a version member:
https://www.w3.org/TR/miniapp-manifest/#version-member
Not sure what exactly should be done about this but FYI regardless.
Contributor guide
No contributing guide indexed for this repository
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 VersionHistory/explainer.md and compare its version-history terminology with the MiniApp Manifest version member specification linked in the issue. Determine the intended resolution for the collision with project maintainers, then update the explainer only after the wording and scope are agreed.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100