errors
Here are 354 public repositories matching this topic...
-
Updated
Oct 29, 2020 - PHP
-
Updated
Nov 10, 2020 - PHP
-
Updated
Nov 13, 2020 - Java
-
Updated
Nov 13, 2020 - Clojure
-
Updated
Oct 23, 2020 - PHP
-
Updated
Aug 24, 2020 - Go
-
Updated
Mar 15, 2019 - Go
-
Updated
Jul 30, 2020 - TypeScript
-
Updated
Nov 5, 2020 - PHP
-
Updated
Nov 13, 2020 - JavaScript
-
Updated
Nov 11, 2019 - Go
-
Updated
May 30, 2017 - JavaScript
-
Updated
Jul 29, 2020 - JavaScript
I'm submitting a ...
[x] Feature request
Current behavior
Actually there is only a reactive way how to invoke an error message, either on submit
or on blur
and both of them depend on a user's action.
Expected behavior
There are cases in some more complex forms where the business logic dictates
-
Updated
Sep 11, 2020 - Python
-
Updated
Oct 27, 2020 - Ruby
-
Updated
Mar 29, 2020 - Go
-
Updated
Nov 13, 2018 - Java
-
Updated
Nov 14, 2020 - TypeScript
-
Updated
Nov 9, 2020 - JavaScript
-
Updated
Nov 13, 2020 - Objective-C
-
Updated
Nov 12, 2020 - Go
Improve this page
Add a description, image, and links to the errors topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the errors topic, visit your repo's landing page and select "manage topics."
For completion, we should offer an
As
method like the one in Go 1.13 errors (https://golang.org/pkg/errors/#As). We should try to make this more reliable than Go's version by preventing panics: "As will panic if target is not a non-nil pointer to either a type that implements error, or to any interface type." Seems like we could just return false in these cases instead.