Jérôme Laban
Jérôme Laban
If we restart this PR, let's use the uno-assets sites.
For breaking changes let's use a branch named `feature/breaking-changes` instead, the CI is already setup properly.
Very nice! Thanks @Youssef1313!
The target code has changed significantly, let's review later when this will get prioritized. Thanks!
@DierkDroth we do not have specific timeframes for this issue to be addressed as we're working based on our current clients priorities. We'll get to it again when we'll have...
@marcpopMSFT would you know if there another related aggregated issue with workloads improvements to track? Features like [workload pinning](https://github.com/dotnet/sdk/issues/27402) or [performance](https://github.com/dotnet/sdk/issues/24843), for instance?
Assuming current users don't override styles using Material-prefixed resources (which currently does not work with Uno), we could invert their definitions for the generic ones to be the original styles...
It's still valid yes.
Some objects are marked as disposable for internal constraints, but it's not something we can change right away as it may be a breaking change (we'll take note to add...