-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use site configs in site #283
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed, please change the site configs so that we have one config for each domain with multiple languages.
dfdf040
to
b44b43a
Compare
…a is needed later for not found page
fb99d82
to
2f9c151
Compare
303ddf6
to
3891531
Compare
9f76ef9
to
f15b3c1
Compare
} | ||
|
||
// Used for getting SiteConfig in server-components where params is not available (e.g. sitemap, not-found - see https://github.com/vercel/next.js/discussions/43179) | ||
export async function getSiteConfig() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure middleware is the right place for this function
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Me neither, but putting it in config.ts
is not possible since this file is called from client components and therefore must not contain server libraries. What about an config.server.ts
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand.
You could put it into it's own file?
We need to change the icon path now that #283 has been merged.
PR Checklist