Modules cannot contain classes with same name

npalardy

Summary

Assuming "modules" form namespaces tow modules cannot contain classes with the same names

(I suspect this has ramifications for how the VCS format is handled as well since two classes with the same name would overwrite each other in the vis format)

Objo Studio Version

26.6.3

Operating System

MacOS 26.5.1 (suspect its on all platforms)

Steps To Reproduce

create new project
add new module (myModule)
add another new module (myModule1)
add a class to the first module (myClass)
add a class to the second module
try to rename myClass1 to myClass

it won't

Expected Result

That I can do this & that IF I need to refer to them I can always use the fully qualified name to do so

Actual Result

can't rename MyClass1 to MyClass

Screenshots, Logs, Or Sample Project

Garry

Thanks Norm. You were right about the underlying problem: Studio was still treating source names as globally unique in a few places, so two module-contained classes with the same short name could collide, and the package/VCS format was also too dependent on the visible source name.

This is now fixed following a pretty major refactor for the next release: https://feedback.objo.dev/feature/449

Source files now have stable IDs, and the compiler/Studio pipeline uses namespace/module-aware source keys, so A.Thing and B.Thing can coexist even though both files are named Thing. The project package format has also been bumped so sources are saved by ID rather than by short name, which avoids overwriting in the exported/VCS representation.

I also fixed the related Studio tooling paths: search results, diagnostics navigation, Go to Definition, debugger source lookup, and run-to-cursor now resolve the fully-qualified source key so Studio opens the correct Thing.

That was a lot of work!