Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 NewErrrors() returns error array #1727

Closed
balcieren opened this issue Jan 21, 2022 · 2 comments 路 Fixed by #1728
Closed

馃悰 NewErrrors() returns error array #1727

balcieren opened this issue Jan 21, 2022 · 2 comments 路 Fixed by #1728

Comments

@balcieren
Copy link
Contributor

@vecpeng did you really test it ? Fiber's router's handler returns just error not []error.

@vecpeng
Copy link
Contributor

vecpeng commented Jan 22, 2022

Sorry, maybe there is a misunderstanding about #1695.

I just thought that it maybe not a good idea to use interface{} instead of string to represent an error because the error in go, indeed, is a string. Moreover, it might introduce backward compatibility issues if someone uses e.Message.
So I just want to add a way to deal with multiple errors in array but it seems haven't been well considered and still should
be discussed. I'm sorry for that.

@balcieren
Copy link
Contributor Author

@vecpeng if you want to examine and support you can look PR #1728

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants