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.

Sign up for GitHub

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

Jump to bottom

Extract message when not encountered with a simple string value #2

Open
edizcelik opened this issue Nov 7, 2019 · 1 comment
Open

Extract message when not encountered with a simple string value #2

edizcelik opened this issue Nov 7, 2019 · 1 comment
Assignees
@jamcry @bilgeyucel
Labels
enhancement New feature or request

Comments

@edizcelik
Copy link

See my comments:
#1 (comment)
#1 (comment)

Let me know if you want to discuss possible algorithms to do this.
@edizcelik edizcelik added the enhancement New feature or request label Nov 7, 2019
@bilgeyucel
Copy link
Contributor

I have found some example error messages. We can test using these datas.

bilgeyucel added a commit that referenced this issue Nov 26, 2019
@bilgeyucel
Improve library by considering non-string cases.
6001a93 
* A long string created with nested key names can be provided as `fieldName` to `getFieldError` function.
* errorDetail can be `string[]`, `ExceptionDetail` or `ExceptionDetail[]`. Consider this in `generateErrorMessage` function
* `genericErrorMessage` is required to initialize `ExceptionTransformer`. `onExceptonExceptioio` is optional.
* Add new util functions to `errorUtils`
* Make more strict type checkings
* Add explanatory informations as comment

Related issue: #2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jamcry jamcry

@bilgeyucel bilgeyucel

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@edizcelik @jamcry @bilgeyucel