Skip to content

Remove legacy old ObjectTree path#1280

Open
seongahjo wants to merge 14 commits into
mainfrom
sa/remove-node-tree
Open

Remove legacy old ObjectTree path#1280
seongahjo wants to merge 14 commits into
mainfrom
sa/remove-node-tree

Conversation

@seongahjo
Copy link
Copy Markdown
Contributor

Summary

Remove legacy old ObjectTree path

How Has This Been Tested?

  • existing tests

@seongahjo seongahjo added this to the 1.2.0 milestone May 11, 2026
@seongahjo seongahjo force-pushed the sa/remove-node-tree branch 12 times, most recently from 91c9e6c to 84e83eb Compare May 15, 2026 06:34
public boolean match(Property property) {
return Types.getActualType(property.getType()).isArray()
|| GenericArrayType.class.isAssignableFrom(property.getType().getClass());
return property.getJvmType().getRawType().isArray();
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

GenericArrayType.class.isAssignableFrom(property.getType().getClass());

This has already been dealt with in the JvmType.

seongahjo added 10 commits May 29, 2026 18:13
Remove the legacy tree package, manipulator, expression, and NodeTreeAdapter
classes. Introduce the new adapter machinery with JvmTypeSystem SPI, migrate
the API surface, and adapt downstream modules and integration tests. Guard
the interface branch in ValueProjectionAssembler against self-recursive
types to prevent StackOverflowError on self-typed wither interfaces.
@seongahjo seongahjo force-pushed the sa/remove-node-tree branch from 1ff4984 to ca479a0 Compare May 29, 2026 09:14
@seongahjo seongahjo changed the base branch from main to 1.2.x May 29, 2026 09:18
@seongahjo seongahjo changed the base branch from 1.2.x to main May 29, 2026 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant