-
-
Notifications
You must be signed in to change notification settings - Fork 452
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
Allow numeric value in tags. #858
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I generally agree with this change, thanks for the PR! Can you add tests so we no longer regress on this issue?
Still missing the documentation of the private function, apart from that it seems fine to me 👍 |
@ste93cry Doc added, sorry for the poor English. |
Any chance to merge this PR? |
@leo108 I did some changes to your PR, please let me know if you're ok with them |
@ste93cry LGTM, Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! Thanks!
It's a very common scene that we use a numeric value as a tag, e.g. user id.
Developers are not always aware that should pass a real string value to Sentry's TagsContext, and InvalidArgumentException thrown in Sentry may not be caught by framework's exception handler because Sentry is called in the exception handler in most cases, thus no error logs in framework nor reports in Sentry, which makes it hard to track error.