DYN-7341 Package compatibility calculation rework #15578
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This PR follows on the recent changes to the PM Search functionality. Following an in-depth discussion with the wider design team regarding how Compatibility should be calculated, this PR contains the changes on the PM Client side.
Current rules affecting the compatibility calculation:
Fall back to Dynamo Sandbox computability version will follow the below rules:
• In Revit look for Revit specific compatibility version. If it is there, use Revit version data and stop.
• In Revit look for Revit specific compatibility version. If Revit specific compatibility info is not present, look if only Dynamo host exists and then use it.
• In C3D look for C3D specific compatibility version. If it is there use C3D version data and stop.
• In C3D look for C3D specific compatibility version. If C3D specific compatibility info is not present, look if only Dynamo host exists and then use it.
• In Sandbox only ever look for Dynamo host. If you find it use it and stop.
Do we support Minimum only range? Yes
• If you only put a Minium, we assume that it is compatible with all point versions of this major version.
• We limit it Major version.
Example Scenario: Min = 2025.0, Max Left Black
Assumption. This will be implemented as any version above 2025.0 and above this (Limited by major version) package works. In 2026 this package will be labeled as incompatible.
For Dynamo we limit to Major versions (2.x, 3.X and so on)
Do we support Maximum only range? No
Min cannot be greater than the max
Version field is a String (not a number)
Declarations
Check these if you believe they are true
*.resx
filesRelease Notes
Reviewers
@zeusongit
@QilongTang
FYIs
@achintyabhat