-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pull fwdata model version from repo #1022
Comments
This one will be easy: any FLEx project will have a {"modelversion": 7000068} I wouldn't put this on the project page as it's highly-technical info and most users won't even know what it means. Maybe in an "Advanced" section that you have to click to reveal. |
Note that LfMerge used to handle model versions of 68 or higher, but it now handles only version 72 (technically 7000072) or higher (which is the current model version as of FLEx 9.0). So anything with model version 68, 69, or 70 is FLEx 8.x (model version 71 was never released). LfMerge never supported model versions earlier than 68. |
LfMerge would probably benefit from a LexBox API that exposes the model number of a project (see sillsdev/LfMerge#343 for details). So this is worth doing so that LfMerge can improve its behavior. |
Update: Decided today that frontend should present this as a FW version, e.g. 8.2 or 8.3 or 9.x. Will keep a haradcoded mapping on frontend, updating it on the rare occasion that FW adds a new model version. |
Describe the feature
Just like we pull in the writing systems and project id, it would be useful to know the model version.
Who is this feature for?
Users of FW lite who might want to sync a project from lexbox
Pages affected
Project page maybe.
The text was updated successfully, but these errors were encountered: