# Call binding with parameters

**URL:** <https://discourse.aurelia.io/t/call-binding-with-parameters/4435>\
**Category:** vNext\
**Created:** [October 10, 2021, 5:57pm UTC](https://discourse.aurelia.io/t/call-binding-with-parameters/4435 "2021-10-10T17:57:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sjarvela](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/sjarvela/32/2145_2.png) [@sjarvela](https://discourse.aurelia.io/u/sjarvela)\
**Post date:** [October 10, 2021, 5:57pm UTC](https://discourse.aurelia.io/t/call-binding-with-parameters/4435/1 "2021-10-10T17:57:36Z")

</div>

According to this issue [.call() binding should allow passing arguments · Issue #271 · aurelia/binding · GitHub](https://github.com/aurelia/binding/issues/271), in Aurelia v1 you could pass parameters in call binding by invoking with an object with named values, and these are used on actual callback.

For example using call binding expecting to get value “param”

```auto
<my-element callback.call="onCallback(param)" />

```

and one is provided in invocation

```auto
this.callback({param: some_value});

```

But this does not seem to work in Aurelia 2, the callback is invoked but no params are passed to the callback function.

Example gist: [Dumber Gist](https://gist.dumber.app/?gist=60bde60b862d2eb39d8e2fab5c3bd75f) : Custom element invokes callback with a value incremented on each click.

Has this changed in Aurelia 2?

---

<div class="post-metadata">

**Author:** ![sjarvela](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/sjarvela/32/2145_2.png) [@sjarvela](https://discourse.aurelia.io/u/sjarvela)\
**Post date:** [October 25, 2021, 10:46am UTC](https://discourse.aurelia.io/t/call-binding-with-parameters/4435/2 "2021-10-25T10:46:50Z")

</div>

So it seems it indeed has changed, did not spot this in migration notes: [Migrating to Aurelia 2 - The Aurelia Docs](https://docs.aurelia.io/resources/migrating-to-aurelia-2#call-binding-some-prop.call-).

Using “$event.param” instead does work, as can be seen in updated gist.
