[JEWEL-755] Remove deprecated and scheduled for removal APIs #2998
Conversation
This file contains hidden or 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
Collaborator
Author
|
Ready to merge |
Collaborator
|
This prevents community from compiling, please fix the usages. |
Collaborator
Author
|
On it |
This removes a number of deprecated and scheduled-for-removal APIs as we near the 2025.1 release. The TextFieldValue-based APIs for text areas and fields have been un-deprecated, since there are still some gaps in functionality in the TextFieldState-based versions (mainly, there is no way to support rich, AnnotatedStrings text yet). These have been marked as experimental, KDocs added, explaining to prefer the state-based versions. Note: ListComboBox deprecated APIs have not been removed yet; together with some other remaining deprecated APIs, they will be removed in IJP 2025.2. Work in JEWEL-726 also impacts this anyway.
rock3r
force-pushed
the
sebp/jewel-755_remove-deprecated-api
branch
from
4d517f3 to
f2367bf
Compare
Collaborator
Author
|
@jakub-senohrabek fixed. The Components showcase dialog was using APIs deprecated a year or more ago; I moved it to the current APIs. |
intellij-monorepo-bot
force-pushed
the
master
branch
from
468d9bd to
082b86a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 removes a number of deprecated and scheduled-for-removal APIs as we near the 2025.1 release. The
TextFieldValue-based APIs for text areas and fields have been un-deprecated, since there are still some gaps in functionality in theTextFieldState-based versions (mainly, there is no way to support rich,AnnotatedStrings text yet).These have been marked as experimental, KDocs added, explaining to prefer the state-based versions.
Note:
ListComboBoxdeprecated APIs have not been removed yet; together with some other remaining deprecated APIs, they will be removed in IJP 2025.2. Work in JEWEL-726 also impacts this anyway.