hxuanyu/intellij-sdk-code-samples
1
0
Fork 0
mirror of https://github.com/JetBrains/intellij-sdk-code-samples.git synced 2025-07-29 09:47:50 +08:00
Code Issues Packages Projects Releases Wiki Activity

api_changes_list_2025.md: cleanup

Browse Source
This commit is contained in:
Yann Cébron 2025-02-26 13:44:19 +01:00
parent 4027aaf15f
commit 5ffbf623bb
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
reference_guide/api_changes_list_2025.md
View File

@ -77,8 +77,8 @@ NOTE: Entries not starting with code quotes (`name`) can be added to document no
### IntelliJ Platform 2025.1 ### IntelliJ Platform 2025.1
The code scheduled with `SwingUtilities.invokeLater` and `SwingUtilities.invokeAndWait` does not hold the write-intent lock Code scheduled with `SwingUtilities.invokeLater` and `SwingUtilities.invokeAndWait` does not hold the write-intent lock
: Consider using an explicit wrapping with `com.intellij.openapi.application.ReadAction.compute` or `com.intellij.openapi.application.WriteAction.run(com.intellij.util.ThrowableRunnable<E>)`. : Consider using an explicit wrapping with [`ReadAction.compute()`](%gh-ic%/platform/core-api/src/com/intellij/openapi/application/ReadAction.java) or [`WriteAction.run(ThrowableRunnable<E>)`](%gh-ic%/platform/core-api/src/com/intellij/openapi/application/WriteAction.java).
Coroutines running under `Dispatchers.Main` do not hold the write-intent lock Coroutines running under `Dispatchers.Main` do not hold the write-intent lock
: To restore the old behavior, consider using `Dispatchers.EDT`. : To restore the old behavior, consider using `Dispatchers.EDT`.