feat: allow spy warning and return emitted state - #144
Merged
Conversation
Tony133
requested changes
Jul 29, 2026
metcoder95
approved these changes
Jul 30, 2026
jean-michelet
approved these changes
Jul 30, 2026
Member
|
Why ping me then merge before I could get to it @jean-michelet ? 😄 |
Member
|
Because Metcoder and Tony accepted, and it is mainly used by us in core so I tough it was ok. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes fastify/fastify#6878
No performance is dropped for adding the spy feature.
Checklist
npm run test && npm run benchmark --if-presentand the Code of conduct