the player moves to the plugin, and src/ has no music code left
officerdev/src/MusicPlayer/ → plugins/music/web/. Engine, state, bar, favourites, lyrics toggle and the library vocabulary — ten files. The barrel stops exporting a player it no longer has, and DashboardLayout stops rendering one. The reasoning that kept it was removed rather than refuted. It stayed because the dashboard widget imported useMusicPlayer from officerdev and the platform cannot import from a plugin, so the state had to stay whatever was decided about the UI. The owner moved the widget into the plugin in the previous commit, and the constraint went with it: the whole remaining dependency became one line, DashboardLayout.tsx:66. MusicPlayerHost is mounted inside the MusicDetail panel. That reads odd until you notice it already returned null on /music — the mini bar is the transport there, and the host existed purely to own the GaplessEngine. In the panel it does exactly that, and the bar code stays intact for whenever there is a slot. [phase 2] Leaving /music unmounts the host and playback stops. Deferred on the owner's call; the bar was "navigating away must not break the application", and that holds: seekPlayer is optional-chained so a call with no host registered is a no-op, registerPlayerSeek clears only its own registration, the host's cleanup destroys the engine and nulls its ref, and the queue is global state so returning to /music remounts and reloads. Solving it properly needs either a shell slot a plugin can contribute to — which reopens "there is no way to export a component" — or the engine hoisted to module scope, which keeps the rule and loses only the off-route controls. Also: the parked widget now imports the player as a sibling rather than through officerdev, and shared.ts stopped being a re-export shim now that the real file is in the plugin. Verified: tsgo clean, 797 tests / 787 pass / same 7. Server restarts, mounts /example /music /offscale, / and /music both 200, and the player is in the built bundle (music.volume, music:lyrics, now-playing?device=web all present — GaplessEngine is a class name and the production build is minified, so grepping for it proves nothing). Not verified by me: what it looks like in a browser. That needs your eyes.
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
import { useMemo, useRef } from 'react';
|
||||
import { useLocation } from 'react-router';
|
||||
import { useDock, MusicPlayerHost, usePanelFullscreen } from 'officerdev';
|
||||
import { useDock, usePanelFullscreen } from 'officerdev';
|
||||
import { useCapabilities } from 'hooks/useCapabilities';
|
||||
import { ErrorBoundary } from '@/components/ErrorBoundary';
|
||||
import { ScreenErrorFallback } from './ScreenErrorFallback';
|
||||
@@ -34,8 +34,10 @@ export function DashboardLayout({ children }: DashboardLayoutProps) {
|
||||
// region below is an `absolute z-2` stacking context and the header is a `fixed z-10` sibling of it. So
|
||||
// "full screen" is cooperative: the panel asks, and the chrome steps aside.
|
||||
const panelFullscreen = usePanelFullscreen();
|
||||
// The content region shrinks when the (in-flow) music dock takes its space; the nav dock measures its
|
||||
// reveal boundary from this element, so it always sits just above whatever's at the bottom.
|
||||
// The nav dock measures its reveal boundary from this element, so it sits just above whatever is at the
|
||||
// bottom of the content region. Written for the in-flow music bar, which used to be rendered here and
|
||||
// left with `plugins/music/` on 2026-08-15; the measurement is not music-specific and still holds for
|
||||
// anything a screen puts at its foot.
|
||||
const regionRef = useRef<HTMLElement | null>(null);
|
||||
|
||||
return (
|
||||
@@ -63,7 +65,6 @@ export function DashboardLayout({ children }: DashboardLayoutProps) {
|
||||
</ErrorBoundary>
|
||||
</div>
|
||||
</section>
|
||||
<MusicPlayerHost />
|
||||
</div>
|
||||
);
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user