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
{{ message }}
This repository has been archived by the owner on Nov 22, 2018. It is now read-only.
You have to use the fat arrow syntax to get access to the event object, which is passed as the second argument. (We could do things like D3 and just stash the event in tagalong.event, too.) If you don't need access to the event and only need access to properties of the data and/or context, you can write a handler like:
<buttont-onclick="click(foo)">{{ foo }}</button>
...which assumes that the data being rendered in that node is an object with a foo property, and the click property is a function of either the data or the rendering context.
The text was updated successfully, but these errors were encountered:
This is in the works in #18, but I wanted to have an issue to track it just in case it doesn't make the next release. Here's how it should work:
You have to use the fat arrow syntax to get access to the event object, which is passed as the second argument. (We could do things like D3 and just stash the event in
tagalong.event
, too.) If you don't need access to the event and only need access to properties of the data and/or context, you can write a handler like:...which assumes that the data being rendered in that node is an object with a
foo
property, and theclick
property is a function of either the data or the rendering context.The text was updated successfully, but these errors were encountered: