Skip to content
#

error-handling

Here are 833 public repositories matching this topic...

deschmih
deschmih commented Apr 24, 2020

Package version eg. v8, v9:

v9

Issue, Question or Enhancement:

If a fqdn starts with an integer f.e. "0.de.pool.ntp.org", the validation fails. The example "0.de.pool.ntp.org" is a valid ntp-server (see https://www.pool.ntp.org/zone/de).

Code sample, to showcase or reproduce:

package main

import(
	"fmt"
    "gopkg.in/go-playground/validator.v9"
)

type Settin
tolvanea
tolvanea commented Nov 9, 2019

(Beginner here, apologies if this is not valid issue.)

This guide example seems not to compile. There's this line:
use failure::err_msg;
but the called macro is:
return Err(format_err!("Input did not begin with $"));

So should the use statement be:
use failure::format_err; ?

Also there's [other example](https://boats.gitlab

venkatvghub
venkatvghub commented Aug 23, 2019

I am trying to use your package for certain use cases and i am confused beyond a point. For instance, i have scenarios for custom errors and error types or error codes etc. I am looking at adding namespaces etc and your documentation is not helping me move forward. Could someone please address it and help me or developers like me understand how to go about using your library better?

morningvera
morningvera commented Feb 18, 2020

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.

lifeiscontent
lifeiscontent commented Apr 21, 2020

Can you guys update your example to include a custom express.js server? The Next.js example you have is too trivial for real world situations so it'd be much more helpful to show how to use bugsnag in cases where you'd have custom routes being served by express. (I know that API routes exist now. but they didn't exist before so it'd be nice to show case common use cases within Next.js)

We're cu

Improve this page

Add a description, image, and links to the error-handling topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the error-handling topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.