fix: Update how nodetypes are calculated for insertion points#2389
Merged
Conversation
🦜 Chachalog
|
gflores-jahia
left a comment
Member
There was a problem hiding this comment.
Code looks ok to me but I think we need to maybe start adding some high level overview of the logic for calculating these nodetypes to make it (somewhat) easier to understand.
|
r3dm1ke
approved these changes
Jun 11, 2026
gflores-jahia
approved these changes
Jun 11, 2026
sdusolle
approved these changes
Jun 11, 2026
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.




Description
Update how nodetypes are calculated for insertion points when contribute types are defined on the node.
Checklist
Source code
Tests
Tip
Documentation to guide the reviews: How to do a code review