Brendonovich
Brendonovich
Explore posts from servers
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
worked great for us implementing breadcrumbs haha
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
yea they're not ready to ship tho
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
i guess you could just do it and pray you don't need any other routes until parallel routes get implemented haha
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
it could work but if you needed any non-drawer routes i don't think it's an option
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
by 'inferred by the actual route' i assume that the props.children of the layout would be the drawer contents
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
if you don't have other stuff you'd need as children it could work
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
yeah i think that's what i meant
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
unless that persistent bit was also part of the layout and the content below was the children, idk
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
hmmm that's kinda getting into parallel routes territory which solid router doesn't support yet, i think i'd just bail out of routing and manage the route state myself for that drawer
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
so you'd have
/chat - implement all the chat ui
/ - blank
/attach - drawer
/chat - implement all the chat ui
/ - blank
/attach - drawer
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
oh i meant drawer sorry
28 replies
SSolidJS
Created by tizu on 2/23/2025 in #support
router: "background" page
i don't think solid router has the features to do this nicely, but a more hacky way might be implementing the whole chat route in a layout and making the page essentially just be empty, then implementing the modal in another route within that layout
28 replies
SSolidJS
Created by McBrincie212 on 2/23/2025 in #support
Having The Same Context Transfer Different Properties
though i think i'd use createContextProvider from solid primitives
57 replies
SSolidJS
Created by McBrincie212 on 2/23/2025 in #support
Having The Same Context Transfer Different Properties
yeah sure
57 replies
SSolidJS
Created by McBrincie212 on 2/23/2025 in #support
Having The Same Context Transfer Different Properties
but idk how much sense that would make if the canvas properties inherit from the base properties in the first place
57 replies
SSolidJS
Created by McBrincie212 on 2/23/2025 in #support
Having The Same Context Transfer Different Properties
since you could overwrite the outer canvas properties context with the base widget context
57 replies
SSolidJS
Created by McBrincie212 on 2/23/2025 in #support
Having The Same Context Transfer Different Properties
also unless you don't need to get the widget context in the canvas
57 replies
SSolidJS
Created by McBrincie212 on 2/23/2025 in #support
Having The Same Context Transfer Different Properties
unless you merge the properties objects no
57 replies
SSolidJS
Created by McBrincie212 on 2/23/2025 in #support
Having The Same Context Transfer Different Properties
then you can pull each of them where necessary
57 replies
SSolidJS
Created by McBrincie212 on 2/23/2025 in #support
Having The Same Context Transfer Different Properties
let the canvas-specific properties exist on their own, and have the widget properties in another area
57 replies