In one of the first example that I wrote I was using Animator.watching instead of Animator.Css.watching.
From @mdgriffith
Oh! you need to use Animator.Css.watching for css. Yeah, unfortunately that’s a subtle one :thinking_face: I was trying to figure out a way to protect this case with types, but wasn’t able to find a nice way.
How about moving Animator.watching to Animator.Inline. Even if the compile still will not detect the problem, as developer I could see the difference. I could also get an error as I would probably not Import Animator.Inline while working with Animator.Css
In one of the first example that I wrote I was using
Animator.watching
instead ofAnimator.Css.watching
.From @mdgriffith
Oh! you need to use Animator.Css.watching for css. Yeah, unfortunately that’s a subtle one :thinking_face: I was trying to figure out a way to protect this case with types, but wasn’t able to find a nice way.
How about moving
Animator.watching
toAnimator.Inline
. Even if the compile still will not detect the problem, as developer I could see the difference. I could also get an error as I would probably not ImportAnimator.Inline
while working withAnimator.Css