541 update the frontend to dis allow use of this filter #583
Conversation
This file contains 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
Kevin101Zhang
force-pushed
the
541-update-the-frontend-to-dis-allow-use-of-this-filter
branch
from
44b7f0d
to
cb07bd5
Compare
|
Still not sure why so many commits are still showing up but the squash will get rid of them anyway I guess. Just make sure to checkout off main after pulling when this is merged, to get rid of whatever those commits are. |
darunrs
approved these changes
Feb 26, 2024
Kevin101Zhang
deleted the
541-update-the-frontend-to-dis-allow-use-of-this-filter
branch
Merged
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.
Looks like the middleware file was pushed on a dev branch and was ignored when testing for CORS options.
Fix: removed- frontend/src/pages/middleware.js
out CORS is created from nextjs looking at next.config.js which is a sibling of package.json