fix(space): replace hardcoded engine version with constant and use FindSpaceLatestVersion #773
+7
−8
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.
This PR addresses a maintainability issue in the space module by:
Replacing the hardcoded engine version string with the named constant EngineVersion103.
Updating the logic for retrieving the latest runtime framework version to use the new FindSpaceLatestVersion method instead of relying on a fixed version number.
These changes improve code clarity, reduce duplication, and make future version updates safer and easier.
Changes:
Use EngineVersion103 constant instead of magic string
Switch to FindSpaceLatestVersion() for latest runtime lookup
Testing:
Verified that space initialization behaves as expected with both known and latest engine versions
All existing unit tests pass