Communicate Version of Plugin to server
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 755
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
Version is terms of either:
- github commit code
- human defined version number
Advantage of commit code: we can easily trace back bugs
Advantage of human version code: we can easily reject and reset updates that came from a version that is too outdated.
Would be great if workbench packages also communicate this information somehow, although I don't see any short term plans to usefully apply this.
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
The issue names no files, tests, or entry points. Start by locating how plugins or workbench packages communicate with the server, then clarify whether the version should be a Git commit or a human-defined number. Done means the chosen version information is communicated consistently and its intended server-side use is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100