fix: /banned
Nav and Foooter links go to correct domain
#1899
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.
Fixes #1898
/banned
is unique like/app.dub.co/(share)/share/[dashboardId]/page.tsx
in that it is on a specific domain but does not have a[domain]
in its path. This means that theNav
andNavMobile
will assume it's ondub.co
and use links relative to the current domain, when in reality it needs to specifydub.co
.This is fixed by manually specifying that the domain is not
dub.co
and instead isdub.sh
withstaticDomain="dub.sh"