feat(nextjs) : add proxy configuration support #2407
Merged
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
catfireparty
changed the title
catfireparty
force-pushed
the
nextjs-proxy-support
branch
from
eb215ac to
894c3e4
Compare
catfireparty
force-pushed
the
nextjs-proxy-support
branch
from
894c3e4 to
51243ff
Compare
jaysoo
reviewed
Feb 5, 2020
jaysoo
reviewed
Feb 5, 2020
catfireparty
force-pushed
the
nextjs-proxy-support
branch
from
75fca70 to
d11d27a
Compare
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Issue
See #2011
This builds on #2372 so I'm expecting that to get merged first and then I can rebase this.
I'm mainly submitting this now to see if the changes I made to the e2e tests work in CI.