Motion component is unable to have a handle to a form object about motion HOT 7 CLOSED

If you can hop on master, this was recently merged: #47

from motion.

@caifara Nice! I'll give that a try.

from motion.

@caifara master does work, however I was unable to call current_target on the event:

[TitleComponent:34660] An error occurred while processing add:
	NoMethodError: undefined method `current_target' for #<Motion::Event:0x00007fa0d8738b80>

however, I was able to switch to using target just fine.

from motion.

@jcoyne current_target was removed in #43 because I don't think it is what we ever wanted. On master (and in the next release), Motion::Event#element will always be the element to which data-motion was added.

I don't want to do a release until I track down what is causing the intermittent CI failures (especially since those are happening much more often now on master).

from motion.

@alecdotninja current_target is still referred to in the README. Should that be removed?

from motion.

@jcoyne Yes, that is a good idea. I really need to get better about documentation. 🙈

from motion.

#47 was released in 0.4.3 and the README has been updated 🎉

from motion.