Repository navigation
Assign model and folder entity IDs centrally in the backend - #54
Merged
fakayser merged 3 commits intoNov 6, 2026
Merged
Conversation
fakayser
changed the base branch from
main
to
feature/plugin-metadata-location
November 6, 2026 11:50
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.
New model and folder entities receive random numeric IDs in the JavaScript-safe range from one backend allocator. Create, clone, source import, migration and implicit folders avoid IDs already used by either entity type. Existing valid IDs survive updates and moves; load/save reject out-of-range IDs and duplicates within each type while allowing historical overlap between model and folder IDs.
Uses the existing entity create/save API and documents its invariants. Solution CI also runs model validation on the merged solution state.
Validation: