Split UseMauiCommunityToolkit #1631
Replies: 4 comments 13 replies
-
@tranb3r, the easy fix on your side is to not call the |
Beta Was this translation helpful? Give feedback.
-
I suspect we might need to migrate to the approach that .NET MAUI uses where we don't auto register the |
Beta Was this translation helpful? Give feedback.
-
I've watched the standup. Let me share my feedback and frustration:
I don't want to be rude (and english not being my mother tongue does not help). I'm really thankful for the hard work (especially knowing that you're not paid by MS, as you keep repeating to everybody). I'm just sharing some frustration, and if by any chance somebody reads it, I'm happy to answer questions and help improve things as much as I can. |
Beta Was this translation helpful? Give feedback.
-
Discussed again on the Monthly stand-up for September and the community agreed this is something that would be nice but with limited resources not something we can progress at this time. However we are a community and more than happy to accept a PR if you feel like jumping in. 😉 |
Beta Was this translation helpful? Give feedback.
-
My app is not using MCT Popup, but the whole Popup code cannot be trimmed from it, because when calling
UseMauiCommunityToolkit
, the popup service is registered for DI, so the trimmer cannot get rid of it.More generally, MCT is a collection of features more or less independant from each others, so it's probably not a good idea to use a single intialization method, if we want the trimmer to be efficient.
To fix this problem, would you consider splitting
UseMauiCommunityToolkit
by feature (or feature group)? (UseMctPopup / UseMctConverters / UseMctViews ...)?Or maybe there is a smarter way to do workaround this issue?
Beta Was this translation helpful? Give feedback.
All reactions