Skip to content
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

[core] Correctly parse status in version names when it exists #1966

Merged
merged 1 commit into from
Apr 7, 2023

Conversation

cbentejac
Copy link
Contributor

@cbentejac cbentejac commented Apr 7, 2023

Description

Version objects were meant to be used only with numerical characters, separated by periods. Now that the version of Meshroom can also contain its status ("develop" when it is in develop mode), the Version class needs to be able to parse the status string (when it exists) as well as the version components.

This PR addresses this by handling the status as a separate string, which is returned in addition to the tuple of integers when the whole version string is parsed in the first place.

This prevents issues when opening files that have been saved with a version like "x.x.x-develop".

@cbentejac cbentejac requested a review from fabiencastan April 7, 2023 10:49
@cbentejac cbentejac self-assigned this Apr 7, 2023
Version objects were meant to be used only with numerical characters,
separated by periods. Now that the version of Meshroom can also contain
its status ("develop" when it is in develop mode), the Version class
needs to be able to parse the status string as well as the version
components when it exists.

The status is handled as a separate string, which is returned in addition
to the tuple of integers when the whole version string is parsed in the
first place.

This prevents issues when opening files that have been saved with a version
like "x.x.x-develop".
@cbentejac cbentejac force-pushed the fix/projectVersions branch from 638d140 to 0b4e38f Compare April 7, 2023 11:29
@fabiencastan fabiencastan added this to the Meshroom 2023.2.0 milestone Apr 7, 2023
@fabiencastan fabiencastan merged commit 3359189 into develop Apr 7, 2023
@fabiencastan fabiencastan deleted the fix/projectVersions branch April 7, 2023 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants