Implemented async dynamic attributes (closes #443).

[radekmie]

In this pull request, I added support for async dynamic attributes, i.e., <img {{getAttributesAsync}}>. As usual, while the Promise is still pending or rejected, an empty state is rendered, i.e., with no attributes at all.

EDIT 2024-01-24: As in this discussion, I also added error handling to all async-related logic. It's based on the Blaze._reportException helper.

[harryadel]

What's holding this PR from merging?

[jankapunkt]

@harryadel as I mentioned in the discussion above, the Promises should be catched and errors piped into the internal error handling, in order to make effective use of APM etc.

[jankapunkt]

Looks good from my end!

[Grubba27]

Should this become a new Release for blaze? or are we waiting for other PRs to make a pr with all these changes?

Like, this and #458 together ?

[radekmie]

I think it'd be best to release it soon, though I'm not sure what's the state of other PRs. @jankapunkt?

[Grubba27]

this will be a minor correct?

[radekmie]

Yes, a minor - there's new functionality here.

[jankapunkt]

I would only add the tests, defined in #458 to make sure this PR also fixes #456

[radekmie]

I thought we agreed to add tests in your #458?

[jankapunkt]

Yes, it's targeting this branch as merge target

[dengribar]

Hi guys! Is this PR going to be merged soon? Are there any blockers?

[radekmie]

I was certain it was already merged and released... @Grubba27, could you take a look?

[Grubba27]

I was certain as well. Let me check that.

[Grubba27]

Well for some reason this got lost 😢

I thought this PR and this #428 were the same. I will merge and make a new minor, v2.9(I'm not sure because this should have come with 2.8; maybe this should be a 2.8.1?)

Also, is there any other PR that should come along this one @radekmie @jankapunkt ?

[radekmie]

I will merge and make a new minor, v2.9(I'm not sure because this should have come with 2.8; maybe this should be a 2.8.1?)

No, this is a new feature - it should be 2.9.

Also, is there any other PR that should come along this one @radekmie @jankapunkt ?

As mentioned above, this one is first, then #458.

[Grubba27]

I've created the #463 PR