-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[Spec] Remove members marked with Obsolete attribute #21
Comments
Should this be done here or in XF repo? I'm asking because #20 was done in XF |
XF repo on main branch @domagojmedo |
@PureWeen there are many tests that use generic BindableProperty.Create, should those tests be removed or changed to use non-generic version of the method? |
I'd say change them to use the non-generic version All the generic version one does is call through to the non-generic one [Obsolete("Create<> (generic) is obsolete as of version 2.1.0 and is no longer supported.")]
[EditorBrowsable(EditorBrowsableState.Never)]
public static BindableProperty Create<TDeclarer, TPropertyType>(Expression<Func<TDeclarer, TPropertyType>> getter, TPropertyType defaultValue, BindingMode defaultBindingMode = BindingMode.OneWay,
ValidateValueDelegate<TPropertyType> validateValue = null, BindingPropertyChangedDelegate<TPropertyType> propertyChanged = null,
BindingPropertyChangingDelegate<TPropertyType> propertyChanging = null, CoerceValueDelegate<TPropertyType> coerceValue = null,
CreateDefaultValueDelegate<TDeclarer, TPropertyType> defaultValueCreator = null) where TDeclarer : BindableObject
{
return Create(getter, defaultValue, defaultBindingMode, validateValue, propertyChanged, propertyChanging, coerceValue, null, defaultValueCreator: defaultValueCreator);
} So if we need to add it back (for some reason) we can just add a Unit test specifically there to validate the generic one |
Layout and VisualElement have obsolete GetSizeRequest method. It says in obsolete attribute to use OnMeasure instead, but OnMeasure is internal and GetSizeRequest is public so we can't just switch usage. How should this be resolved? |
Hmmmmm @domagojmedo I would leave that one for now We'll replace that one with the layout updates... I'm not sure off hand with that one because our So the fix might just be to make GetSizeRequest internal ? But I'm not really sure off hand |
Description
Remove members marked with the
Obsolete
attribute.Core
Maps
Xaml
UWP
iOS
Android
Android Renderer Constructors
Each renderer which existed as of 2.4 has an obsolete constructor which does not take a Context parameter.
Backward Compatibility
Any applications or libraries still using the obsolete properties or methods will have to update.
Difficulty : Low
Mostly this just means deleting methods and properties which already call through to other methods and properties. In a few cases we may also need to remove non-public members which are no longer used.
The text was updated successfully, but these errors were encountered: