-
Notifications
You must be signed in to change notification settings - Fork 277
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
Expose fields (or add access methods) of MessageNotFoundErr #306
Comments
What is your use case for wanting access to the underlying fields? |
For now, I am doing structured logging and would prefer to have the language and message key as fields. In the future, I intend to send custom alerts to ease the translation flow. |
Any intention of exposing this? 🙏🏾 |
I don't have a strong objection. If you want to open a PR I will review it. |
stephenafamo
added a commit
to stephenafamo/go-i18n
that referenced
this issue
Nov 18, 2023
nicksnyder
pushed a commit
that referenced
this issue
Nov 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With
errors.As
, it is now possible to detect the error, but since the fields are private, there is no way to extract the structured details without resorting to string parsing.The text was updated successfully, but these errors were encountered: