-
Notifications
You must be signed in to change notification settings - Fork 471
Move C# Markup Extensions from Forms to Toolkit #499
Comments
Still blocked by xamarin/Xamarin.Forms#12136 |
Here is the source for C# Markup including CSharpForMarkup Part 2 PR features, in a single commit: VincentH-Net/Xamarin.Forms@939150d
|
@VincentH-Net I would like to know how I can help you to move the CSharpForMarkup to the XCT. XCT was recently added to the .NET Foundation and a Support document has been created https://github.com/xamarin/XamarinCommunityToolkit/blob/main/Support.md |
Thanks for your offer @jsuarezruiz! This is how we could get it done:
Tbc the Xamarin.Forms.Core API's that C# Markup itself needs access to are: Internal
Private
In addition, the C# Markup unit tests need to access below API's. If that would be preferred by the team, we could opt to keep below API's as they are, and use reflection in XCT unit tests to access them. Since we won't ship the unit tests, that would not introduce any risks for XCT users. Xamarin.Forms.Core.UnitTests Internal:
Xamarin.Forms.Core private API's on
|
I have submitted a PR to XCT yet as it needs to support Xamarin.Forms 5.0. The original PR for Popup Control in Xamarin Forms is xamarin/Xamarin.Forms#9616. As of today the only outstanding PR I have to Xamarin.Forms is opening up a few APIs to allow UWP support xamarin/Xamarin.Forms#12279. Popup Control Ready Platform
I haven't submitted any PR to XCT for the Popup Control, once we get a branch that support Xamarin.Forms 5.0 I can start submitting PRs |
I think that we can create a branch here targeting Forms 5.0. FYI, The last time that I did it I face some issues with |
Summary
The C# Markup Extensions in its current form need to move from Forms into the Toolkit.
We want to add this in a separate package from the main one and therefore also a separate (new) namespace
The text was updated successfully, but these errors were encountered: