Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.77%. Comparing base (28bc599) to head (71c98ea).
Report is 563 commits behind head on dev.

@@            Coverage Diff             @@
##              dev    #9967      +/-   ##
==========================================
+ Coverage   89.82%   90.77%   +0.94%     
==========================================
  Files         412      407       -5     
  Lines       11878    12578     +700     
  Branches     2364     2454      +90     
==========================================
+ Hits        10670    11418     +748     
+ Misses        681      598      -83     
- Partials      527      562      +35     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

We could also leave the old one in place, and then it wouldn't be a breaking change, but I feel like the original one is broken and it not what you would want most of the time and we should not encourage it's usage.

Changed my mind, and decided to go for ComponentBase + UnsafeAccessor as then you can use it on normal pages and won't require to implement IComponentException like I had in EventUtil1Test.razor.

I wonder if this could be used for #6104 and #6413

I wonder if this could be used for #6104 and #6413

Yes

The last one that's still impacting me is the menu items. They're still triggering renders even with AutoClose="false"

The last one that's still impacting me is the menu items. They're still triggering renders even with AutoClose="false"

Interesting, maybe something else there triggering re-render?

Are we removing EventUtil.AsNonRenderingEventHandler(...) ? It is v8 after all, we can break and this is easy to migrate.

Are we removing EventUtil.AsNonRenderingEventHandler(...) ? It is v8 after all, we can break and this is easy to migrate.

That was my question in #9967 (comment)
Do you want to keep it considering that this wouldn't propagate the exception to ErrorBoundary and people might not expect it(we can add it to xmldoc, but not everyone is reading that) or we just remove it and only the "correct" new API will exist. There is also always a chance that someone from community will PR with using the wrong version and that gets missed in the review.

Added to v8.0.0 Migration Guide #9953