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
Copy file name to clipboardExpand all lines: src/bunit.core/Rendering/TestRenderer.cs
+1-5Lines changed: 1 addition & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -80,11 +80,7 @@ public IRenderedComponentBase<TComponent> RenderComponent<TComponent>(ComponentP
80
80
}
81
81
catch(ArgumentExceptionex)when(string.Equals(ex.Message,$"There is no event handler associated with this event. EventId: '{eventHandlerId}'. (Parameter 'eventHandlerId')",StringComparison.Ordinal))
82
82
{
83
-
varbetterExceptionMsg=newArgumentException($"There is no event handler with ID '{eventHandlerId}' associated with the '{fieldInfo.FieldValue}' event "+
84
-
"in the current render tree. This can happen, for example, when using cut.FindAll(), and calling event trigger methods "+
85
-
"on the found elements after a re-render of the render tree. The workaround is to use re-issue the cut.FindAll() after "+
86
-
"each render of a component, this ensures you have the latest version of the render tree and DOM tree available in your test code.",ex);
0 commit comments