# Is there a fear of release?

**URL:** <https://discourse.aurelia.io/t/is-there-a-fear-of-release/4877>\
**Category:** vNext\
**Created:** [August 16, 2022, 8:43am UTC](https://discourse.aurelia.io/t/is-there-a-fear-of-release/4877 "2022-08-16T08:43:33Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![MaximBalaganskiy](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/maximbalaganskiy/32/831_2.png) [@MaximBalaganskiy](https://discourse.aurelia.io/u/MaximBalaganskiy)\
**Post date:** [August 8, 2023, 1:50am UTC](https://discourse.aurelia.io/t/is-there-a-fear-of-release/4877/21 "2023-08-08T01:50:51Z")

</div>

@ghiscoding Copied some examples. One thing I wasn’t sure of is the row detail, but it seems to be working fine.

---

<div class="post-metadata">

**Author:** ![ghiscoding](https://yyz1.discourse-cdn.com/flex027/user_avatar/discourse.aurelia.io/ghiscoding/32/1199_2.png) [@ghiscoding](https://discourse.aurelia.io/u/ghiscoding)\
**Post date:** [August 8, 2023, 3:56am UTC](https://discourse.aurelia.io/t/is-there-a-fear-of-release/4877/22 "2023-08-08T03:56:56Z")

</div>

@MaximBalaganskiy thanks a lot for the work you started, would it be possible to maybe create a PR on the project? I created a `next` branch that you can create a PR against and I can do more work and commits on that branch until it’s finalized. I know it’s a big ask since the directory structure is all different, I assume you started from scratch, but it’s a bit hard for me to test and debug things when most examples are missing and folders are in totally different places.

For example, I tried to add back Example 15 because of a TODO you commented about and I’m having an error message about a possible infinite loop which I have no clue where that actually comes from, I’m not sure if it’s Aurelia 2 related error or not.

 ![image](https://canada1.discourse-cdn.com/flex027/uploads/aurelia/original/2X/6/6c5865f8e8444e1b8516d657502ac3061ff25241.png)

EDIT

I found the infinite loop to actually be caused by the onXYZ Custom Events that are needed for Aurelia-Slickgrid to work properly (i.e. `on-aurelia-grid-created.delegate="aureliaGridReady($event.detail)"`). That definitely will have to be supported eventually. Actually it seems to be the previous use of `.delegate` which probably changed in Au2… yup it was changed to `.trigger()`, it might be a good idea to throw a proper error in Au2 instead of an infinite loop in the template processing

We could talk about all of this in private chat or in GitHub Discussions on Aurelia-Slickgrid project. I don’t necessarily want to bother everyone else with this topic. Thanks 🙂

[Previous page](https://discourse.aurelia.io/t/is-there-a-fear-of-release/4877.md?page=1)