Only apply CORS to /backends in Functions emulator #4295
Merged
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.
Description
When adding the /backends route to the Functions emulator, we enabled CORS so that the Emulator UI could call the new endpoint. However, we did so too broadly, and caused some unexpected behavior changes (like #4294 ). This instead only applies CORS to just the /backends route.
I also noticed that we were unnecessarily using 'dataMiddleware' for this route, so I removed that.
Fixes #4294