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: Print a warning in case the middleware didn't run on a request but APIs from next-intl are used #1045

Merged
merged 1 commit into from
May 3, 2024

Conversation

amannn
Copy link
Owner

@amannn amannn commented May 3, 2024

No description provided.

@amannn amannn marked this pull request as ready for review May 3, 2024 13:36
Copy link

vercel bot commented May 3, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
next-intl-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 3, 2024 1:38pm
next-intl-example-app-router ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 3, 2024 1:38pm

@amannn amannn changed the title fix: Ensure warning about the middleware not matching a request is printed fix: Print a warning in case the middleware didn't run on a request but APIs from next-intl are used May 3, 2024
@amannn amannn merged commit 8149955 into main May 3, 2024
6 checks passed
@amannn amannn deleted the fix/logging-for-unmatched-request branch May 3, 2024 13:45
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.

None yet

1 participant