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

feat: Skeleton.read & RefSkel.read with kind adjustment #1398

Closed

Conversation

phorward
Copy link
Member

@phorward phorward commented Jan 31, 2025

Allows to automatically convert a key in Skeleton.read/RefSkel.read to the kind of the specific skeleton. This is useful to rewrite old data, especially in relations.

Allows to configure `Skeleton.read`/`RefSkel.read` to adjust the kind of a key when the given key does not match. This is useful to rewrite old data, especially in relations.
@phorward phorward added the feature New feature or request label Jan 31, 2025
@phorward phorward changed the title feat: Skeleton.read(weak=True) (+RefSkel) feat: Skeleton.read & RefSkel.read with adjust_kind-flag Feb 3, 2025
ArneGudermann
ArneGudermann previously approved these changes Feb 3, 2025
@phorward phorward added the Priority: High After critical issues are fixed, these should be dealt with before any further issues. label Feb 4, 2025
sveneberth
sveneberth previously approved these changes Feb 4, 2025
Using `id_or_name` enforces adjustment of kindName
@phorward phorward dismissed stale reviews from sveneberth and ArneGudermann via 6a6b0a8 February 4, 2025 13:56
@phorward phorward changed the title feat: Skeleton.read & RefSkel.read with adjust_kind-flag feat: Skeleton.read & RefSkel.read with kind adjustment Feb 4, 2025
@phorward phorward requested a review from sveneberth February 4, 2025 13:57
@phorward
Copy link
Member Author

phorward commented Feb 4, 2025

Solved project-specific.

@phorward phorward closed this Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request Priority: High After critical issues are fixed, these should be dealt with before any further issues.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants