Currently, you get the values in the following order: oldValue, newValue
This was done to match attributeChangedCallback. However, in practice this is not as ergonomic. It's often the case that you do not care about the previous value, causing code like this: myObserver(_, value).
This is pulled into a separate issue since it will cause a sweeping change of all code leveraging observers.
Currently, you get the values in the following order:
oldValue, newValueThis was done to match
attributeChangedCallback. However, in practice this is not as ergonomic. It's often the case that you do not care about the previous value, causing code like this:myObserver(_, value).This is pulled into a separate issue since it will cause a sweeping change of all code leveraging observers.