Ban some desktop versions
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
How to use GitHub
- Please use the 👍 reaction to show that you are interested into the same feature.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
My problem is related to desktop publications that regularly met regression (ie: 4.0.0 for Windows with VirtualFiles): some desktop versions produce such a mess that it is better to totally exclude them from sync.
Describe the solution you'd like
Because minimum.supported.desktop.version and maximum.supported.desktop.version exist, I suppose another parameter like excluded.desktop.versions could be created.
Example:
'minimum.supported.desktop.version' => '3.15.0',
'maximum.supported.desktop.version' => '4.0.99',
'excluded.desktop.versions' => '3.12.4,3.12.5,3.13.0,3.14.0,3.15.1,3.16.1,4.0.0',
Describe alternatives you've considered
With this parameter, We could allow a range of desktop versions AND exclude some in between.
Additional context
I also suggest to desktop team to sample desktop distribution, but this is not enough if I want to totally exclude 4.0.0 for example.
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 locating where minimum.supported.desktop.version and maximum.supported.desktop.version are read and enforced in the server. Define how excluded.desktop.versions should match versions between those bounds, then verify the behavior against the supplied examples and existing version checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100