We do not consider this inspection to be production-ready yet,
so we make it internal-only to prevent regular users from active
interactions with it for the time being.
(cherry picked from commit 1b4cdfe0bd0da227ef0d1ab39e81f923375a39ae)
IJ-MR-165997
GitOrigin-RevId: b229d165f45f747cac30fafafeaa1d75a1cc98fd
- as a consequence, after dumb mode the modules are recreated in `K2IDEProjectStructureProviderCache.invalidateAllModuleCaches` and `LLSelectingCombinedSymbolProvider.selectFirstElementInClasspathOrder` fails to choose `precedence` because `providers` might still have old modules
- the next step would be to ensure that all caches with KaModule, track dumb mode as well
^KTIJ-34563 fixed
(cherry picked from commit 7347322c235cec0d24b44829527c4bb0a792acdf)
IJ-CR-166185
GitOrigin-RevId: 31a2c7f6e804a4f7db2ed138f80f65b5d242d36e
* Added a description for the "Python" group of Settings
* Added a description for the "Type Renderers" settings page
* Added a description for the "External Documentation" settings page
* Added a helpId for the "Type Renderers" settings page
(cherry picked from commit 29e93e8dd7fc7f54adea825b60cf8d95540fc6b0)
IJ-CR-166515
GitOrigin-RevId: f8fd3f2ca9d6e2d34077a5424673adeb66bc05d1
* Added additional type-check in the is_real_file function
(cherry picked from commit 8cec0ce0ce98eba7fce2c75a1352675e36b84d87)
IJ-CR-166515
GitOrigin-RevId: c592571ff2c3e81eaf21d948a614d3af7644333f
The approach with concurrent launches is the main suspect
for various tool window glitches, like the content not showing
up or several tabs without names appearing in the header.
UI code is not designed to be concurrent, so when launching
several rebuilds, we need to wait until the previous one
has finished one way or another. But because of that
it seems that we don't even need concurrent launches.
To keep the cancel-on-content-manager-dispose semantics,
introduce a nested coroutine scope, cancelling it when
the tool window content manager is disposed.
Add some logging there as well so we can figure out
what's going wrong in case anything doesn't work.
(cherry picked from commit 743ce422c4c75d51635e7f459e68b83ec72d27c3)
IJ-CR-166271
GitOrigin-RevId: f9e72354fae924545004ef2308ad65c793c8ede4
Fix RIDER-84956: Add raw commandline support based on CreateProcessW
Merge-request: IJ-MR-163129
Merged-by: Sergey Vardanyan <sergey.vardanyan@jetbrains.com>
(cherry picked from commit 0b1eae71a5efcaeb98f868f0a4bd7640211d0f29)
IJ-CR-166077
GitOrigin-RevId: bb4243ad03c946e39ae6f74e0ad1c23ff0a7135f
1. Mark as frontend-only to prevent getting it from backend
2. Explicitly disable frontend action in CWM
(cherry picked from commit d396b6d537eeb7cf0a6fa63c73db7b30e5d8fc44)
IJ-MR-166286
GitOrigin-RevId: 3338cfca87e43c00bcd112720523f7a2d34d58ca
After the first update, toolbars suppress fast track updates.
However, now that auto-resizing relies on fast track being
enabled, this sometimes prevents auto-resizing.
Fix by suppressing fast track only after the update was
applied and auto-resize already happened.
(cherry picked from commit b4d433766883034be90ce13893928938a4d7faf4)
IJ-CR-165957
GitOrigin-RevId: 3872ef32058ec70dceb570bad9b442be2cf4acb9
This reverts commit e29d54c0c0d449e8229160365008b4ba88235a90.
Reverted because of a better fix.
(cherry picked from commit 457aa8978a77dad90507df3781361d764025bd77)
IJ-CR-165957
GitOrigin-RevId: 0e9765e5023b5838bf416b39b1916ee63a1332c9
After disabling resize for toolbars with disabled fast track,
it now affects these popup toolbars that show the hidden actions.
It happens because SUPPRESS_FAST_TRACK is auto-set in
updateActionsImpl when firstTimeFastTrack is true.
For such toolbars fast track is useful to have
and auto-sizing is a must-have, so we just force
fast track by setting SUPPRESS_FAST_TRACK to false.
(cherry picked from commit d37eb67f6bbf506d347d76433f581706861e9107)
IJ-CR-165957
GitOrigin-RevId: ed0805f18509f1fb5565d0bda2ae9a437ceea9ff
So, external plugins may use it.
(cherry picked from commit 75cf70a16f21c6f722fad314ed391c4b77438cba)
IJ-CR-166213
GitOrigin-RevId: 0e7347a34e1280531d206a0ff37e9f1256862f7d
Support the classic terminal, new terminal (gen1) and the reworked terminal (gen2).
This method is the fast solution, but probably not final, since we plan to have a better public API for the Reworked Terminal. So, mark it as experimental.
(cherry picked from commit 1bae3499a909b4b9447af0b734a87eda53e8d67d)
IJ-CR-166213
GitOrigin-RevId: f0b7e77880e38ef3d2ac4b1c4ba19e99fcc7da06
Revert "[java] IDEA-360282 Use implicit class declaration for a new Java 25 project"
This reverts commit f21990af11c320d373023658866859f61c3c93fd.
(cherry picked from commit ec865d097aa1196ef5061a473d3cc2ba2eb7ca99)
IJ-CR-166010
GitOrigin-RevId: 400df4916c884fee63cacf53b0228faf1a1f1cfa
The corresponding extension point is used in Java plugin only, but declared in LangExtensionPoints.xml, so the class should be in lang.impl module to avoid ClassNotFoundException.
The class itself isn't marked as Internal, because otherwise DevKit plugin will highlight usages of the corresponding extension as internal (see IJPL-172788).
(cherry picked from commit af9caf8d2e8e1b181509f5a47601d0d2bd2f5eb2)
IJ-CR-166054
GitOrigin-RevId: 513730d3e8b811b153349afbc3e026c4db4149df
Now it's also not necessary to explicitly update a speedsearch pattern and register `Git.Branches.Popup.SpeedSearch`, as all actions will be performed with the search text field set as a context component.
(cherry picked from commit 84508b29f754d8442fdd4299531b7c5e493fd8de)
IJ-CR-166091
GitOrigin-RevId: f22f59d051c2bab78393b2fd90258ecd00777053
These dependencies aren't used in code, and they shouldn't there since intellij.spellchecker.xml was extracted to a separate module. Also, this change is needed to avoid failures in JetBrainsGatewayIdeStructureTest after 'intellij.spellchecker' is added to Gateway (to fix AT-2832).
Explicit dependency on intellij.platform.backend is added to ensure that the module isn't included in the frontend process (before dependency on intellij.platform.backend came as transitive).
(cherry picked from commit 75e55fda55205b8cc10ff08b93a7b2af1aefee43)
IJ-CR-166031
GitOrigin-RevId: f378c3348f97299aa55287f75dc5b46903ee67d7
A separate module with trigger model was introduced with a local up-to-date ML API version, so we don't have to update the ML API in other projects in scope of the trigger model integration task.
Co-authored-by: Aral de Moor <aral.de.moor@jetbrains.com>
Co-authored-by: Gleb Marin <gleb.marin@jetbrains.com>
Merge-request: IJ-MR-165229
Merged-by: Vladimir Fedorov <890readrid@gmail.com>
GitOrigin-RevId: 9ca30d6dfb42cc635d72eedadfce6314573e46ec
