#IJPL-187199 Fixed
#IJPL-186195 Fixed
Cause of which is a threading exception on loading `.getContent()`
(cherry picked from commit eec980bbaf107e2caa4f08c5150e74b773e0593b)
IJ-CR-163488
GitOrigin-RevId: 602b08ae6568932027bd7db7f7aa00227cf22765
The existing gitlab.community and github.community modules that describe community versions of plugins with less functionality included do still exist intentionally. This is required for external developers to be able to build IDE from community project sources and get both plugins working there out of the box. Thus community plugins are still listed in IdeaCommunityProperties and PyCharmCommunityProperties. This part is only required for third-party folks. As for internal builds, they employ a build context produced by `org.jetbrains.intellij.build.IdeaUltimateBuilderKt.createBuildContextForCommunityProduct` which in turn prefers github.ultimate and gitlab.ultimate plugin distributions over community ones
(cherry picked from commit e8233c7133d63abe3aefa684cc57ed9bad9fee64)
IJ-CR-156816
GitOrigin-RevId: c7058bba3734d4509a66d48b338466f5e0e7b05d
Technically, currently this is the same, because 'intellij.yaml.backend' module is registered as the embedded module of YAML plugin, so it's loaded by the main plugin classloader. However, dependency on the module is more explicit. Also, we may need to temporarily convert 'intellij.yaml.backend' to an optional module to reuse the same plugin.xml for the frontend process.
GitOrigin-RevId: bf96ed0c60cb335fdb0e592a619e1425cb322f2b
There is no need to use a longer name for the common part after the old 'intellij.yaml' was renamed to 'intellij.yaml.backend'. Also, this allows keeping the old main module name for the YAML plugin after moving 'plugin.xml' to this module.
GitOrigin-RevId: 1509abc515a490c949097dedbcf26fb12925c101
This module isn't used in a frontend variant of the IDE, so it should use the '.backend' suffix for consistency and to avoid confusion.
References from the build script to the 'intellij.yaml' module aren't changed in this commit because 'intellij.yaml.editing' module will be renamed to 'intellij.yaml' in the next commit, and plugin.xml will be moved to it.
GitOrigin-RevId: 1c535a9a02bdccd89f46cdad71e34064b1dab854
Changed the loading type of the `intellij.vcs.gitlab` module to "embedded" in both Ultimate and Community plugin configurations. This ensures that the module is loaded only when explicitly required and improves plugin initialization behavior [AI generated].
Fix the problem "com.intellij.diagnostic.PluginException: Class org.jetbrains.plugins.gitlab.ui.GitlabCiIconProviderKt must not be requested from main classloader of org.jetbrains.plugins.gitlab plugin. Matches content module (packagePrefix=org.jetbrains.plugins.gitlab., moduleName=intellij.vcs.gitlab). [Plugin: org.jetbrains.plugins.gitlab]"
also see 4a5b0c098eb361c15a2bbb323da78df0f7e9f99d
GitOrigin-RevId: 6dbd78a33d45a7800caf2b8d269297cd903a4971
it is a squash commit of several commits. It was made to avoid code appearance in the community part of the repository and because the gitlab-plugin layout (structure of the related modules, files, etc.) was changed. The messages of the squashed commits are:
- IJPL-84197 GitLab CI: add navigation from `stage` usage to its declaration
- IJPL-84197 GitLab CI: bidirectional navigation refs<->declarations for "stages" using Symbol API
- IJPL-84197 GitLab CI: completion for "stages" via Symbol API
- IJPL-84197 GitLab CI: rename "stages" in "in-place" mode via Symbol API considering "broken" ranges
"broken" ranges - ranges, that are passed into Pointer restoration function (see `GitLabCiStageSymbol.createPointer`) from IDE at the moment when Enter is pressed in the end of Rename action in "in-place" mode. "end" values of such ranges are equal to "start" values, and this looks like not expected behavior. And hacks are needed to consider these "broken" ranges.
- IJPL-84197 GitLab CI: support quoted strings for "stage"-values as well as plain text
- IJPL-84197 GitLab CI: fix problem: "stage declaration is not highlighted when cursor is on usage"
plus some refactoring
- IJPL-84197 GitLab CI: turn on registry flag
for simpler future tests running
- IJPL-84197 GitLab CI: tests for `stage` symbol editor support
- IJPL-84197 GitLab CI: move code to gitlab-ultimate module
GitOrigin-RevId: f49ea2717bfa4764abefee5ef81a9e474690754a
Without this, I expect it to stay stuck until commits
can be fetched. Better to show something early.
GitOrigin-RevId: b1ef74d6306981ad177ec08d806600fb5d9cf220
it is only a first step of sawing "intellij.vsc.gitlab" module into a "intellij.vsc.gitlab" module and a "intellij.vsc.gitlab.community" plugin-module
(cherry picked from commit 2711465aa7fdd6261dab7f55d2aaf2a5c1c78c7d)
IJ-CR-150169
GitOrigin-RevId: a0a40647ffba431448b1997d51071d141ed555f3
Just pass around data, let's stop the secret encapsulation of VMs.
Also moves UI-data closer to UI by moving some text selection
GitOrigin-RevId: d403779fffa6365d97a2510451774b0c693622a3
List loading structure is moved into GitLabCloneRepositoriesListViewModel.kt
This makes it possible to load lists in parallel and
is generally the structure more closely representing the visual structure.
Should help with refactoring the list rendering in the future
(I believe the list should be rendered as a list of lists somehow, but currently it's flattened into one big list.
The current implementation seems hacky if you ask me)
GitOrigin-RevId: 806c32bc5ab314ee0003eabe13036c413944387f
#IJPL-161183 Fixed
This should make it easier to avoid timeouts,
but we're definitely not guaranteed to prevent them at this moment.
Also splits up the queries for snippets and clone dialog.
These should require and fetch much much less data than full project data.
This is because we may have to fetch hundreds if not thousands
of projects.
GitOrigin-RevId: 06e979df8922533858c117f5cfe2362bb6cb0ab3
With this fix, we'll be able to add the gitlab classes to the ultimate tests classpath which will help to detect bugs caused by interfering extensions from all the plugins
GitOrigin-RevId: 485f87a181d8f93dc569c443fff2e7cfd70f53a5
