-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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: prevent serialisation of private component fields #5208
Merged
soloturn
merged 11 commits into
develop
from
feat/no-private-component-field-serialisation
Mar 3, 2024
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
a0c9384
feat: prevent serialisation of private component fields
BenjaminAmos 873fe5b
log line shorter for ComponentTypeHandlerFactory
soloturn d992dbf
Merge branch 'develop' of https://github.com/MovingBlocks/Terasology …
BenjaminAmos 7178325
feat(TypeHandlerLibrary): do not serialise private fields in ObjectFi…
BenjaminAmos 7701cc1
fix: fix ObjectFieldMapTypeHandlerFactoryTest tests
BenjaminAmos 9aa53fe
fix: fix TypeSerializerTest tests
BenjaminAmos 456efca
fix: fix VectorTypeSerializerTest tests
BenjaminAmos 2cbdba0
fix: fix BlockAreaTypeHandlerTest tests
BenjaminAmos 6f284d7
style: fix checkstyle issues in TypeSerializerTest.java
BenjaminAmos 17b2b9e
Merge branch 'develop' into feat/no-private-component-field-serialisa…
jdrueckert 91c852f
fix: catch setter errors explicitly in ObjectFieldTypeMapHandler
BenjaminAmos File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
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.
Why fluent API usage here?
I would expect
getName()
andgetTypeName()
to be O(1) so pretty much neglectable... also this is not on the happy path so it's not expected to be evaluated often...In my test run, I got the warning only twice:
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.
I did not make that change. @soloturn pushed 873fe5b to this branch, possibly as a well-intentioned fix for a newly-introduced checkstyle warning.
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.
okay, guess it might've been a PMD warning in that case.
I'd prefer suppressing the warning (suffix with
//NOPMD
) here due to the above-mentioned reasons.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.
i am a little confused - git blame says @BenjaminAmos changed that line. commit 873fe5b changed ComponentTypeHandlerFactory, different file, but the change looks the same? in case i really did this, feel free to undo. 2 warnings, one line too long, and one for the logger are there in the line before.