#4040 - Ability to store preferences from client-side code #4041
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
reckart
added
⭐️ Enhancement
* Added `ClientSideUserPreferencesProvider` interface that can be implemented by Spring components to permit access to certain preference keys including their validation * Added LoadPreferences and SavePreferences calls to the JS API * If an annotation has no label, show the layer name in the annotation browser sidebar instead of "No label" * Removed unused DiamEditorBase class
reckart
force-pushed
the
feature/4040-Ability-to-store-preferences-from-client-side-code
branch
2 times, most recently
from
c8759de to
cab66e3
Compare
* Fix dependencies * Store the other annotation browser sidebar preferences a well
reckart
force-pushed
the
feature/4040-Ability-to-store-preferences-from-client-side-code
branch
from
cab66e3 to
0f5b49e
Compare
reckart
deleted the
feature/4040-Ability-to-store-preferences-from-client-side-code
branch
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.
What's in the PR
ClientSideUserPreferencesProviderinterface that can be implemented by Spring components to permit access to certain preference keys including their validationHow to test manually
Automatic testing
Documentation