Currently the transition object can have a ‘function’ key to specify a custom timing function. In retrospect this name isn’t as descriptive as I wanted it to be. Also, using the key ‘function’ in the template can throw off the code highlighting in the VS code plugin.
In order to address these 2 issues, we should rename the key ‘function’ to ‘easing’
This will be a breaking change. As we are in beta, I don’t think we need to follow a full deprecation path. But we should log a descriptive error when the old ‘function’ key is used in a transition object, to make it straightforward to make the necessary fixes in the app code.
Currently the transition object can have a ‘function’ key to specify a custom timing function. In retrospect this name isn’t as descriptive as I wanted it to be. Also, using the key ‘function’ in the template can throw off the code highlighting in the VS code plugin.
In order to address these 2 issues, we should rename the key ‘function’ to ‘easing’
Before:
After:
This will be a breaking change. As we are in beta, I don’t think we need to follow a full deprecation path. But we should log a descriptive error when the old ‘function’ key is used in a transition object, to make it straightforward to make the necessary fixes in the app code.