Repository navigation
fix(nuxt): stop warning about the missing registry without a layout - #29
Conversation
|
I'm not sure if we should do this since normally named slots declared for a layout don't belong to the page itself. Is it possible to consider rendering slots on the page component's parent component when there is no registry? (not sure if it's possible) |
Fair, I'm not attached to the second commit. I asked Claude to try your idea. Its findings:
What I'm after is simpler: I want to unit test pages without hand-written wrappers in every spec. This patch may well be the wrong shape for it — it does make the page render markup that isn't its own. Maybe it belongs in The first commit is independent of all this — I can keep just that one in this PR and move the slots part to a separate issue. |
|
Yes, just keep the first commit for now. |
a88676d to
3c91988
Compare
|
Done. I also created issue #30. |
Follow-up to #25: v0.5.7 made rendering a page without a layout work, but Vue still warns on every page.
LayoutSlotandLayoutSlotsForwardcallinject(injectionKey)with a single argument, and Vue warns whenever the key is missing and no default was passed (it checksarguments.length > 1), so every mounted page logsinjection "Symbol(dxup:layout-slots)" not found.useLayoutSlots()a few lines above already passesnull.