Skip to content

Conversation

@jsumners
Copy link
Member

@jsumners jsumners commented Aug 4, 2019

This is the same as #1786 except targeting the master branch.

Checklist

  • run npm run test and npm run benchmark
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message and code follows Code of conduct

Add FastifyError.toString to display code in `console.log(error)`
@jsumners jsumners added the internals Change that won't impact the surface API. label Aug 4, 2019
@jsumners jsumners mentioned this pull request Aug 4, 2019
4 tasks
Copy link
Member

@StarpTech StarpTech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@delvedor delvedor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As said by @mcollina, I agree that errors should be identified via the code property, but if someone is currently relying on the name property this will be a breaking change.

We are facing two options:

  • release the breaking change and be ready to release a patch if we see that this is causing too many issues.
  • close this pr, since this change will land in any case in v3

I'm fine with either option.
👍 for merge it in master
😄 for postpone this to v3

@jsumners
Copy link
Member Author

jsumners commented Aug 5, 2019

@fastify/fastify see comment above for a vote ^

@mcollina
Copy link
Member

mcollina commented Aug 9, 2019

It seems we are at a stall, maybe we should err for the safety case and wait for v3.

@jsumners jsumners closed this Aug 9, 2019
@delvedor delvedor deleted the separate-error-code branch August 11, 2019 11:00
@Eomm Eomm mentioned this pull request Aug 27, 2019
4 tasks
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

internals Change that won't impact the surface API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants