You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our Ice property code currently supports deprecating one property by another, with the assumption they're still "compatible". We then also perform an extra check when setting a property which is deprecated by another one. If "Foo" is deprecated by "Bar", we actually set "Bar" (silently) but warning that "Foo" is deprecated.
I think we should remove this functionality.
Deprecating something means it still works for now but will be removed in the future. We actually just set a different property making it confusing if you attempt to look this property up in the future.
If we do want to deprecate a property we should mark it as deprecated and still actually check it in code. In a future release we would remove it and its use entirely.
The text was updated successfully, but these errors were encountered:
Originally posted by @externl in #2100 (comment)
Our Ice property code currently supports deprecating one property by another, with the assumption they're still "compatible". We then also perform an extra check when setting a property which is deprecated by another one. If "Foo" is deprecated by "Bar", we actually set "Bar" (silently) but warning that "Foo" is deprecated.
I think we should remove this functionality.
The text was updated successfully, but these errors were encountered: