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

Fixed ambiguous namespace resolution and matching non-public types #1877

Merged
merged 4 commits into from
Nov 3, 2024

Conversation

tomasherceg
Copy link
Member

Resolves #1876

Copy link
Member

@exyi exyi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

10 lines, 10 comments 😅 Anyway, the public type check might be a bit annoying, if someone has all viewmodels internal, which is currently allowed. However, it should be quite simple to migrate and the compilation page will show all the errors, so I think this is a good change for version 5. Alternatively, we could add a list of "InternalsVisibleFrom" assemblies to DotvvmConfiguration, but I guess it is not really worth the added complexity.

I don't know why are the tests failing... more specifically, why the culture whitespace thing stopped being a problem and why tests which don't even exists are failing? 🤦

@exyi exyi added this to the Version 5.0 milestone Oct 27, 2024
@tomasherceg tomasherceg force-pushed the fix/binding-ambiguous-namespaces branch from 32d8396 to e09359d Compare November 3, 2024 09:59
@exyi exyi merged commit 86a56fc into main Nov 3, 2024
14 checks passed
@exyi exyi deleted the fix/binding-ambiguous-namespaces branch November 3, 2024 11:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Binding translator should ignore non-public classes and report ambiguous imports
2 participants