Repository navigation
Release 2.1.1: description refresh and backend-assigned entity IDs - #50
Merged
Merged
Conversation
Assign model and folder entity IDs centrally in the backend
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release 2.1.1 fixes complete entity description refresh and assigns model and folder IDs centrally in the backend.
Complete refresh adopts changed or removed source descriptions, accepts matching descriptions from multiple sources and rejects conflicts. Sources-only refresh and entities without external sources retain their descriptions.
New model and folder entities receive random JavaScript-safe numeric IDs from one allocator across create, clone, source import, migration and implicit folders. Existing valid IDs survive updates and moves; loading and saving reject invalid IDs and duplicates within each entity type while preserving historical overlap between model and folder IDs. Clients retain the backend's returned IDs and use the existing create/save flow.
PR #54 is merged into this release branch, which also includes current main. Package and lockfile are at 2.1.1; the solution schema remains 2.0.0. Release notes cover both changes and compatibility. The frontend consumer update is oraylis/datam8-frontend#68 and should follow this release PR.
Validation of the integrated release:
After merging into main, the protected v2.1.1 tag on the merged commit can run the existing release workflow. No version tag or release has been created by this change.