* Added logging split to track if slicing or formatting was applied
* Introduced a field to indicate whether the table is new or legacy
GitOrigin-RevId: 9cfec94b7b3ef83f5134eea4287f8abfe347f702
Switch FilePathDiffTitleCustomizer to GridBagLayout, as GroupLayout isn't fully supported in RD
GitOrigin-RevId: 80c15edf70e0ad81cb1423a42d361894014997f9
Try to install Poetry and Pipenv if they are not found
Merge-request: IJ-MR-141839
Merged-by: Egor Eliseev <Egor.Eliseev@jetbrains.com>
GitOrigin-RevId: 535426090df23b358ba61a9e21c2f0954c201945
During the highlighting, resolve happens which needs a scope. To compute the scope, the project structure is needed, to compute which the plugin dependencies structure is needed, to compute which the plugin.xml needs to be analyzed along with all its includes. These includes are cached in the user data of the included file, which is retained by weakref in FileManagerImpl, meaning it's gced very often, clearing all its caches in the process. To make these caches live a bit longer, retain all these included files by soft ref in FileIncludeManager
GitOrigin-RevId: 6fc22d23af0e82756b34173a8e03680c46cfb899
Moved RoundedLineBorder to a new file and renamed it to RoundedLineBorderWithBackground.
Let's use this rounded border for In-Editor generation popup
GitOrigin-RevId: b4365f7cefe24eca1e77d83c1f329e069788b226
Before, a contribution scope was a scope of opening. Any launch inside `Open` freezes the opening process. Now, the contribution scope lives while View is alive.
GitOrigin-RevId: c96bc10804d15b3996057f265b89a9c988aa1eb4
Computing `basicContext.useSiteModule.directFriendDependencies` for each `isDefinitelyInvisibleByPsi`
is wasteful, so we avoid that by caching the result
^KTIJ-31260 Fixed
GitOrigin-RevId: 9e4641c4b53a4a48a18dbeb8d05e028df9a578fa
Thanks to `Component.showingScope` we can now collect data from a flow as long as the component is displayed.
At the same time, we can emit data back using `MutableStateFlow`.
We can now move UI-specific logic to the View Model and cover it with tests, leaving a View as simple as possible.
GitOrigin-RevId: 7df699d1428506e8c42cffebbb31702fd248e004
Previously, it was shown on every application restart. Now it's shown once for every plugin installed.
This works by storing a custom property in `PropertiesComponent` indicating that a notification for a specific plugin was shown or not
^KTIJ-31266 fixed
GitOrigin-RevId: 3e7796d5890a7cfcb762d479b69d2c5ab04d53cb
Fixes IDEA-357662 Create Property intention for missing property key doesn't allow to select the local resource bundle
GitOrigin-RevId: d27d7a7bf4b18f2b78b008b079307fa47bccecf4
- created dedicated script dependencies modules should use project jdk when it's applicable, otherwise we add a new library to a project which is required to be indexed.
^KTIJ-31243 fixed
GitOrigin-RevId: 9870e658b148ebbe4cf85d340b1928f8e0f191dd
+ Notification about VFS recovery was introduced in 241, to make user aware that delayed IDE startup is due to VFS recovery, which was caused (likely) by user actions (e.g. kill-ing the IDE).
That notification causes a lot of misunderstanding/misinterpretation, so it was quickly disabled by default in Release versions, left only in EAP -- and a bit later disabled in EAP also. Now it is time to get rid of it entirely
GitOrigin-RevId: 34d923db37fdfd16fbb13cf5bbf915d2bca5664f
It was accidentally increased before by excluding one of the
borders from the header itself. It was needed to fix some
issues with double borders.
GitOrigin-RevId: d72aec35cacda4a033ec4698a91b5fa58c334bd5
When the "Set user scale factor" message pops up,
it's hard to reason about the scaling factor origin.
Add debug logging to the call sites to make it easier.
GitOrigin-RevId: 56c19b319a44d57edb850166bde2d47b52b235b4
