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

[Trimming] Feature switch: IVisual scanning support #2

Conversation

simonrozsival
Copy link
Owner

WIP: This PR will be rebased on main and moved to the official MAUI repo once dotnet#19310 is merged

Description of Change

The current implementation of VisualTypeConverter.InitMappings isn't trimming-safe. It scans all types in all assemblies and looks for classes implementing the IVisual interface.

Customers should instead use the existing [assembly: Visual(...)] attribute to register their IVisual classes.

TODO: We need a follow-up issue to update the docs -- although I can only find Xamarin Forms docs... where are the MAUI docs?
TODO: Link to docs

Issues Fixed

Contributes to dotnet#19397, fixes dotnet#4937

@simonrozsival simonrozsival force-pushed the feature-switch-ivisual-assembly-scanning branch from 447b0e3 to 83cf16c Compare February 6, 2024 12:57
Copy link

github-actions bot commented Feb 6, 2024

Thank you for your pull request. We are auto-formatting your source code to follow our code guidelines.

@simonrozsival simonrozsival deleted the feature-switch-ivisual-assembly-scanning branch February 6, 2024 15:58
@github-actions github-actions bot locked and limited conversation to collaborators Mar 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant