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
// Currently this also happens if you forget to add the hidden field, but soon we'll do that automatically, so the
21
+
// message is designed around that.
22
+
thrownewInvalidOperationException($"Cannot dispatch the POST request to the Razor Component endpoint, because the POST data does not specify which form is being submitted. To fix this, ensure form elements have an @onsubmit:name attribute with any unique value, or pass a Name parameter if using EditForm.");
// This might only be possible if you deploy an app update and someone tries to submit
28
+
// an old version of a form, and your new app no longer has a matching name
29
+
thrownewInvalidOperationException($"Cannot submit the form '{handlerName}' because no submit handler was found with that name. Ensure forms have a unique @onsubmit:name attribute, or pass the Name parameter if using EditForm.");
thrownewInvalidOperationException($"There is more than one named event with the name '{assignedName}'. Ensure named events have unique names. The following components both use this name: "
// This should not be possible, as the system doesn't create a way that the location could be wrong. But if it happens, we want to know.
92
+
thrownewInvalidOperationException($"The named value frame for component '{componentId}' at index '{frameIndex}' unexpectedly matches a frame of type '{frame.FrameType}'.");
// This won't be possible if the Razor compiler requires @onsubmit:name to be used only when there's an @onsubmit.
118
+
thrownewInvalidOperationException($"The {frame.NamedValueName} value in component {componentId} at index {frameIndex} does not match a preceding event handler.");
// Currently this also happens if you forget to add the hidden field, but soon we'll do that automatically, so the
116
-
// message is designed around that.
117
-
thrownewInvalidOperationException($"Cannot dispatch the POST request to the Razor Component endpoint, because the POST data does not specify which form is being submitted. To fix this, ensure form elements have an @onsubmit:name attribute with any unique value, or pass a Name parameter if using EditForm.");
// This might only be possible if you deploy an app update and someone tries to submit
123
-
// an old version of a form, and your new app no longer has a matching name
124
-
thrownewInvalidOperationException($"Cannot submit the form '{handlerName}' because no submit handler was found with that name. Ensure forms have a unique @onsubmit:name attribute, or pass the Name parameter if using EditForm.");
// This should not be possible, as the system doesn't create a way that the location could be wrong. But if it happens, we want to know.
139
-
thrownewInvalidOperationException($"The named value frame for component '{componentId}' at index '{frameIndex}' unexpectedly matches a frame of type '{frame.FrameType}'.");
// This won't be possible if the Razor compiler requires @onsubmit:name to be used only when there's an @onsubmit.
165
-
thrownewInvalidOperationException($"The {frame.NamedValueName} value in component {componentId} at index {frameIndex} does not match a preceding event handler.");
0 commit comments