-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ProjectPackages should allow subpackages #23
Comments
Hey @levinalex - this seems like it would be a solid addition to the library. If you want to take a stab at it that would be great. If not then someone will get around to this soon! |
fjferrer
added a commit
to fjferrer/bugsnag-go
that referenced
this issue
Nov 9, 2015
Fixed by #25. Thanks! |
thank you 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
right now
ProjectPackages
usesfilepath.Match
to check which parts of the stacktrace to filter:However, wildcards (because of
Filepath.match
) will only be expanded into a single 'directory'. This matchesexample.com/foo/bar
andexample.com/foo/baz
but notexample.com/foo/bar/fred
orexample.com/foo/bar/fred/bar
.(my workaround to that was to say
{"example.com/foo/*", example.com/foo/*/*", example.com/foo/*/*/*"}
but that is brittle and ugly)It would be nice if it was possible to match all subpackages explicitly (maybe via
"example.com/foo/**"
?)I'd take a stab at implementing this if you are open to it
The text was updated successfully, but these errors were encountered: