Commit graph

7 commits

Author SHA1 Message Date
Marco Beretta
1b7ab8a523
🎨 feat: Paint Inline Deployment Themes From the First Frame (#17203)
* feat: Paint Inline Deployment Themes From the First Frame

* test: Point the Theme Pin Mutations at the Provider Bundle
2026-10-19 21:28:48 +02:00
Marco Beretta
37ec4b56c9
🎨 feat: Paint the Operator Theme on a First-Ever Visit (#16962)
* feat: Paint the Operator Theme on a First-Ever Visit

The server embeds the deployment's base interface.theme in the HTML shell, with both modes the build resolved for a bundled name, so the boot script and the first commit of DeploymentTheme paint it before /api/config answers. A tab's owned cache still outranks it, shared links skip it, and a request scoped by a trusted X-Tenant-Id header gets the shell without it.

* test: Type the Inline Shell Theme Fixture as Raw JSON

* test: Tag the First-Visit Scenarios Literally

* fix: Ignore a Theme Boot File That Is Not an Object

* fix: Keep the Base Theme for a Tenant Header the Config Rejects

* fix: Report a Theme Boot File That Exists but Cannot Be Read

* fix: Embed the Base Config Theme in the Experimental Shell

* test: Stand In the Shell Theme for an Owned Copy Whose Session Ended
2026-10-14 13:16:44 +02:00
Marco Beretta
5cb396e85c
👋 feat: Optional Greeting Heading and Footer-Free Welcome Screen (#17055) 2026-10-14 11:10:08 +02:00
Marco Beretta
e216f08289
🌗 feat: Hand the Colour Mode Over on an Entry Link (#17056) 2026-10-13 12:27:28 +02:00
Marco Beretta
4519fe09ae ⚖️ refactor: Move Policy Links to the Signup Consent (#16138)
(cherry picked from commit 1bfaa5f96f)

Original-PR: https://github.com/LibreChat-AI/LibreChat/pull/16138
2026-10-01 03:46:16 +00:00
Marco Beretta
8e6e6f062d
🪧 fix: Emit the Configured-Footer Answer With the HTML Shell (#15886)
* 🪧 fix: Emit the Configured-Footer Answer With the HTML Shell

The chat surface lays out against whether the deployment configured a footer
(customFooter, privacy policy, terms of service). The client answered that from
localStorage — whatever the last resolved `/api/config` recorded — so the answer
was a guess on a first-ever visit and could be stale for a deployment whose
configuration changed.

The backend already knows when it serves client/dist/index.html, so it says so
there: `injectConfiguredFooterBootstrap` writes `hasConfiguredFooter` into
`window.__LIBRECHAT_CONFIG__` ahead of the app's own scripts, once at boot from
the base app config, and the client reads it on its first render instead of
remembering the last answer. The `configured-footer` storage atom is gone.

Client and server share one predicate (`hasConfiguredFooter` in
librechat-data-provider) so the two cannot disagree, and the shell injection is
generalized (`injectBootstrapConfig`), with the query-devtools flag now going
through it.

* 🧷 fix: Keep Bootstrap Values Literal and State the Shell's Contract

`injectBootstrapConfig` passed its script as a replacement string, so a `$&`,
`$1` or `$'` inside an injected value was expanded by `String.replace` instead
of reaching the client. Both insertion points take a replacement function now,
and the spec reads its values back off the global through an explicit result
type rather than an unchecked dictionary.

The shell answers from the deployment's own configuration, which a per-tenant,
role or user override of `interface.privacyPolicy` or `termsOfService` can
disagree with — `/api/config` resolves the caller's and the client prefers it.
That contract was overstated in three comments ("a deployment-lifetime fact",
"the same one the config will give"); they now say what the answer is and what
resolves the rest. Two scenarios cover the disagreement end to end: a document
served without the answer, and a policy link only this caller's config carries.
2026-09-13 21:53:54 -04:00
Ravi Kumar L
865e1da857
⚙️ refactor: lazy-load React Query Devtools (#13639)
* perf(client): lazy-load query devtools

* fix: keep query devtools deps lazy

* fix: address query devtools review findings

* fix: exclude query devtools from pwa precache

---------

Co-authored-by: Danny Avila <danny@librechat.ai>
2026-06-10 13:06:20 -04:00