IntelliJ supports .idea/.name files for storing a project name independently of the directory containing the project.
This is useful for deps.edn projects because deps has no project-name concept and Cursive currently derives both the project and module names from the containing directory. In Git worktrees and Jujutsu workspaces, the same logical project may be checked out into directories with different names. This can cause shared run configurations and other module-name-based settings to stop resolving correctly.
Cursive should continue using the containing directory name on initial import. On subsequent imports or opens, when the top-level deps.edn is in the same directory as .idea, Cursive should use the contents of .idea/.name for both the IntelliJ project name and the corresponding top-level module name.
Nested deps.edn modules should retain their existing directory-derived naming and collision-disambiguation behavior. If a nested module conflicts with the custom top-level name, the top-level name should remain fixed and the nested module should be disambiguated.
IntelliJ supports
.idea/.namefiles for storing a project name independently of the directory containing the project.This is useful for
deps.ednprojects because deps has no project-name concept and Cursive currently derives both the project and module names from the containing directory. In Git worktrees and Jujutsu workspaces, the same logical project may be checked out into directories with different names. This can cause shared run configurations and other module-name-based settings to stop resolving correctly.Cursive should continue using the containing directory name on initial import. On subsequent imports or opens, when the top-level
deps.ednis in the same directory as.idea, Cursive should use the contents of.idea/.namefor both the IntelliJ project name and the corresponding top-level module name.Nested
deps.ednmodules should retain their existing directory-derived naming and collision-disambiguation behavior. If a nested module conflicts with the custom top-level name, the top-level name should remain fixed and the nested module should be disambiguated.