Skip to content
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

Svelte 5 Migration 2 #671

Merged
merged 8 commits into from
Jan 3, 2025
Merged

Svelte 5 Migration 2 #671

merged 8 commits into from
Jan 3, 2025

Conversation

sebadob
Copy link
Owner

@sebadob sebadob commented Jan 1, 2025

#642

This PR will take care of the way theming will be done in the future.

The old / current way of handling it is pretty inefficient and does not allow to easily use light / dark theming in combination with client branding. It also does not compress dynamically created HTML with SSR inserted values.

@sebadob sebadob marked this pull request as draft January 1, 2025 12:36
@sebadob
Copy link
Owner Author

sebadob commented Jan 3, 2025

The current code implements the whole backend for the new theming approach with all database migrations, structs, API endpoints, caching, pre-compression, and so on. The new (default rauthy) theme has been implemented into the app.html in the UI and will from now on always be preloaded and fetched (and cached).

PUT and DELETE endpoints do exist as well already and are working. However, a UI component to modify the theme has not been implemented yet and will be built in a future PR, when the clients config view in the Admin UI is being migrated to Svelte5 as well. Doing it now would mean to do the work twice, which does not make much sense.

@sebadob sebadob marked this pull request as ready for review January 3, 2025 12:38
@sebadob sebadob merged commit c44db4b into main Jan 3, 2025
@sebadob sebadob deleted the sv5-new-theme-setup branch January 3, 2025 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant