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
What is the current behavior of feature you are looking to change?
As previously agreed upon, the aliased commands that predated the model engine redesign started in #990 are meant to go away as part of 0.19.0.
What is the proposed behavior of feature you are looking to change?
Aliased commands will no longer work and the new commands must be used.
What is the benefit of the design change you are proposing?
The commands are simple aliases introduced to ease the transition from the old commands - but we don't want to maintain these indefinitely. The new ones being the only ones are better from both a UX and maintainability POV.
What is the current behavior of feature you are looking to change?
As previously agreed upon, the aliased commands that predated the model engine redesign started in #990 are meant to go away as part of
0.19.0.What is the proposed behavior of feature you are looking to change?
Aliased commands will no longer work and the new commands must be used.
What is the benefit of the design change you are proposing?
The commands are simple aliases introduced to ease the transition from the old commands - but we don't want to maintain these indefinitely. The new ones being the only ones are better from both a UX and maintainability POV.
If applicable, how would backwards-compatability be handled?
We called this out as part of the
0.17.0release, so backwards-compatability is not a concern here.Additional context
Related to #1419