Skip to content

Named interface detection accidentally picks up nested declarations in nested interfaces scenario #662

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.

Sign up for GitHub

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

Jump to bottom
Closed
odrotbohm opened this issue Jun 18, 2024 · 0 comments
Closed

Named interface detection accidentally picks up nested declarations in nested interfaces scenario #662

odrotbohm opened this issue Jun 18, 2024 · 0 comments
Assignees
@odrotbohm
Labels
in: core Core module meta model type: bug Something isn't working
Milestone
1.2.1

Comments

@odrotbohm
Copy link
Member

Back-port of GH-650.
@odrotbohm odrotbohm added in: core Core module meta model type: bug Something isn't working labels Jun 18, 2024
@odrotbohm odrotbohm added this to the 1.2.1 milestone Jun 18, 2024
@odrotbohm odrotbohm self-assigned this Jun 18, 2024
odrotbohm added a commit that referenced this issue Jun 18, 2024
@odrotbohm
GH-662 - Fix named interface detection in case of nested packages.
d66259e 
If named interfaces are declared in nested packages, the name detection might accidentally pick up the names declared in child packages. We now deliberately only inspect the base package.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@odrotbohm odrotbohm

Labels
in: core Core module meta model type: bug Something isn't working
Projects
None yet
Milestone
1.2.1
Development

No branches or pull requests
1 participant
@odrotbohm