Fix bug in supportedOperations property initialization #172
Conversation
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 commit addresses a critical bug in the getSupportedOperations method where modifications to the returned list did not affect the underlying supportedOperations property. Previously, if the supportedOperations property was not initialized, getSupportedOperations would return a new ObservableList that was not bound to the supportedOperations property, leading to discrepancies in data handling.
|
dlemmermann
approved these changes
May 10, 2024
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.
This commit addresses a critical bug in the getSupportedOperations method where modifications to the returned list did not affect the underlying supportedOperations property. Previously, if the supportedOperations property was not initialized, getSupportedOperations would return a new ObservableList that was not bound to the supportedOperations property, leading to discrepancies in data handling.