sillsdev / sillsdev/languageforge-lexbox
reject commits from newer versions of FW Lite
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9
- Forks
- 8
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 49
Description
Describe the feature
Right now I could author a commit in say 06-24-2025 of FW Lite, and 05-24-2025 would happily take that change and maybe not work correctly. Since FW Lite is ever green we expect the user to just upgrade to 06-24-2025 in that case. There should be good error handling to explain to the user that they need to upgrade to version x in order to sync latest. However this could result in a poisoned commit from say 2050 and then no one would be able to download the project as their client would reject that commit. To protect against that the server should reject commits from a version greater than latest. In develop we should probably disable that.
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 at the server-side commit and sync handling entry point; the issue does not name a file or test. Trace how the client version is received and compared with the latest version. Done means newer-version commits are rejected with an upgrade message, future-dated commits cannot poison downloads, and develop has the intended restriction disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100