feat: refactor site configuration handling#430
Merged
Conversation
- Update site configuration to be fetched dynamically from the server at runtime, removing the need for frontend environment variables during build. - Introduce new hooks (`useSiteConfig` and `useSiteConfigValue`) to access site configuration values throughout the client. - Modify various components and pages to utilize the new site configuration methods for displaying site name, description, avatar, and pagination size. - Update documentation to reflect changes in environment variable usage and site configuration management. - Remove legacy environment variable handling in the client build process.
|
🧹 Preview deployment has been cleaned up. The temporary preview environment for this PR has been deleted. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
useSiteConfiganduseSiteConfigValue) to access site configuration values throughout the client.