Goland project names are not informative

[bdleitner]

I'm not sure if this is an issue with the bazel plugin or with Goland more generally (or both). Unlike IJ, Goland doesn't seem to have a simple way to control a project's name (there is no name field in Project settings, for example).

In IJ, when I import a bazel project, I can name it and get descriptive names in the load window:

In Goland, on the other hand, all of the bazel projects use .project-data-dir and .workspace from Project Structure (note that there is no place to set the name):

To give the following view when opening a project:

All of the projects have the same name, so I have to look at internals of the path to figure out the right one, and this is doable but annoying.

[JamesRTaylor]

All projects in Open Recent menu list have the same name: .project-data-dir, workspace. Makes it very difficult to open the right project.

[sgowroji]

Hello @bdleitner, Could you please confirm are you still seeing this with the latest release and also for non bazel projects ?

[JamesRTaylor]

I'm still seeing this with the latest bazel plugin, @sgowroji

[bdleitner]

Hello @bdleitner, Could you please confirm are you still seeing this with the latest release and also for non bazel projects ?

Yes, I'm still seeing it in the latest version. Non-bazel projects are not (and were never) affected.

[Vertexwahn]

I am having the same issue: GoLand 2022.3.3 (on macOS M1), Plugin version: 2023.02.22.0.1-api-version-223

[Vertexwahn]

The issue still exists in: GoLand 2023.2 Build #GO-232.8660.185, built on July 26, 2023 macOS 13.5

[JamesRTaylor]

It's crazy to me that the tooling for Bazel is so bad. It's been a year, and you can't fix a bug preventing the name of the project from appearing correctly? We've moved away from Bazel because of it's lack of usability and tooling (like many projects I've seen), so not interested anymore, but what is going on with this project?

[mai93]

Goland is not explicitly supported by the plugin, please refer to the documentation; IDEs section. The issue is marked P3 which means we can accept a PR to fix it.

[github-actions[bot]]

Thank you for contributing to the IntelliJ repository! This issue has been marked as stale since it has not had any activity in the last 6 months. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-maintainer". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

[bdleitner]

@bazelbuild/triage not stale, still happening.

[Vertexwahn]

Still relevant!