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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: use internal request id header vs "X-Request-Id" #529

Merged
merged 1 commit into from
Mar 26, 2024

Conversation

kettanaito
Copy link
Member

@kettanaito kettanaito commented Mar 26, 2024

* Ideally, come up with the Interceptor-level mechanism for this.
* @see https://github.com/mswjs/interceptors/issues/378
*/
export const INTERNAL_REQUEST_ID_HEADER_NAME =
Copy link
Member Author

@kettanaito kettanaito Mar 26, 2024

Choose a reason for hiding this comment

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

This is a workaround until we can implement a better detection of nested interceptors (tracked in #378).

@kettanaito kettanaito changed the title fix: use internal request id header vs "x-request-id" fix: use internal request id header vs "X-Request-Id" Mar 26, 2024
@kettanaito kettanaito merged commit 28e533c into main Mar 26, 2024
1 check passed
@kettanaito kettanaito deleted the fix/378-replace-request-id branch March 26, 2024 09:24
@kettanaito
Copy link
Member Author

Released: v0.26.12 🎉

This has been released in v0.26.12!

Make sure to always update to the latest version (npm i @mswjs/interceptors@latest) to get the newest features and bug fixes.


Predictable release automation by @ossjs/release.

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

Successfully merging this pull request may close these issues.

1 participant