8f0bb94caf
The root layout replaced the entire app with the SetupScreen whenever the config was incomplete (missing gallery.yaml or Immich credentials) — including /admin, which lives under the same root layout. That locked users out of the very tool that fixes an incomplete configuration. The middleware now forwards the request pathname via an x-pathname header, and the root layout skips the setup screen for admin paths, so /admin renders normally (login when ADMIN_PASSWORD is set, the enable-hint otherwise) while every other route keeps showing the setup instructions. Fixes #326 Co-authored-by: ralksta <ralksta@users.noreply.github.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
28 lines
871 B
TypeScript
28 lines
871 B
TypeScript
import { describe, it, expect } from 'vitest';
|
|
import { isAdminPath } from '@/lib/admin/paths';
|
|
|
|
// The root layout must keep /admin reachable while the app is in setup mode
|
|
// (missing gallery.yaml or Immich credentials) — the admin panel is the tool
|
|
// that fixes exactly that state (#326).
|
|
describe('isAdminPath', () => {
|
|
it('matches /admin exactly', () => {
|
|
expect(isAdminPath('/admin')).toBe(true);
|
|
});
|
|
|
|
it('matches nested admin paths', () => {
|
|
expect(isAdminPath('/admin/settings')).toBe(true);
|
|
});
|
|
|
|
it('does not match the homepage', () => {
|
|
expect(isAdminPath('/')).toBe(false);
|
|
});
|
|
|
|
it('does not match sibling paths that merely start with "admin"', () => {
|
|
expect(isAdminPath('/administration')).toBe(false);
|
|
});
|
|
|
|
it('treats a missing pathname header as non-admin', () => {
|
|
expect(isAdminPath(null)).toBe(false);
|
|
});
|
|
});
|