-
Notifications
You must be signed in to change notification settings - Fork 281
feat(java): support multi-dimensional array field serialization in xlang meta shared mode #2314
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
Conversation
@@ -466,6 +466,10 @@ private ClassInfo buildClassInfo(Class<?> cls) { | |||
return info; | |||
} | |||
|
|||
private boolean handleArray(Class<?> cls) { | |||
return !TypeUtils.getArrayComponent(cls).isPrimitive() || !cls.getComponentType().isPrimitive(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems this can be simplified into:
return !TypeUtils.getArrayComponent(cls).isPrimitive() || !cls.getComponentType().isPrimitive(); | |
return !cls.getComponentType().isPrimitive(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And I prefer inline it into the caller, instead of creating a new method
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…ang meta shared mode (apache#2314) ## What does this PR do? support multi-dimensional array field serialization in xlang meta shared mode ## Related issues apache#2277 ## Does this PR introduce any user-facing change? - [ ] Does this PR introduce any public API change? - [ ] Does this PR introduce any binary protocol compatibility change? ## Benchmark --------- Co-authored-by: Shawn Yang <[email protected]>
What does this PR do?
support multi-dimensional array field serialization in xlang meta shared mode
Related issues
#2277
Does this PR introduce any user-facing change?
Benchmark