Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Namespace inside global namespace doesn't always resolve relative to it #4049

Closed
timotheeguerin opened this issue Jul 30, 2024 · 0 comments · Fixed by #4050
Closed

Namespace inside global namespace doesn't always resolve relative to it #4049

timotheeguerin opened this issue Jul 30, 2024 · 0 comments · Fixed by #4050
Assignees
Labels
breaking-change A change that might cause specs or code to break bug Something isn't working needs-area triaged:core
Milestone

Comments

@timotheeguerin
Copy link
Member

timotheeguerin commented Jul 30, 2024

If the nested namespace start with the same as the file namespace it will merge with it inside of defining something nested under

Playground Link

namespace Foo.Bar;

model A {
  b: global.Foo.Bar.Baz.B;
}

namespace Foo.Bar.Baz {
  model B {}
}

CSharp to compare doesn't allow it actually
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change A change that might cause specs or code to break bug Something isn't working needs-area triaged:core
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant