🦋 Changeset detected

Latest commit: 001a235

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

I still don't get it. When I have nested folder and there I created layout-foo.svelte
Now I after update 307 I can use in the same folder => [email protected]
But I have there layout from foo and default layout also. How does it work for index.svelte in nested folder then?
When I want to use as a reset layout as before?

I still don't get it. When I have nested folder and there I created layout-foo.svelte Now I after update 307 I can use in the same folder => [email protected] But I have there layout from foo and default layout also. How does it work for index.svelte in nested folder then? When I want to use as a reset layout as before?

I'm currently having this issue. Default layout still appears and wraps around the named layout. Is there a solution you have found?

[Edit]: I placed the named layout in /routes instead of having it in the nested folder and it works as intended here.

]: I placed the named layout in /routes instead of having it in the nested folder and it works as intended

That doesn't seem to be the case for me. I'm trying to implement an auth guard behavior and been racking my brain on it a bit.

I'm trying to use the default layout as an auth guard to redirect unauthenticated users for all pages, and then using a named __layout-public.svelte to opt-out of authentication for pages like login/sign-up. I have console logs inside the __layout files and it seems on my login/sign-up pages, both the named layout and default layout are both firing.

My file structure is like this:

/routes
  __layout.svelte
  __layout-public.svelte
  /login
     [email protected]

]: I placed the named layout in /routes instead of having it in the nested folder and it works as intended

Interesting, that doesn't seem to be the case for me. I'm trying to implement an auth guard behavior and been racking my brain on it a bit.

I'm trying to use the default layout as an auth guard to redirect unauthenticated users for all pages, and then using a named [email protected] to opt-out of authentication for pages like login/sign-up. I have console logs inside the __layout files and it seems on my login/sign-up pages, both the named layout and default layout are both firing.

My file structure is like this:

/routes
  __layout.svelte
  __layout-public.svelte
  /login
     [email protected]

That's pretty much what my new structure looks like. I had originally tried doing:

/routes
  __layout.svelte
  /page
      __layout-test.svelte
      [slug]@test.svelte

but it was wrapping the default __layout.svelte (contains header and footer) around the "test" layout.

I switched to this structure:

/routes
  __layout.svelte
  __layout-test.svelte
  /page
      [slug]@test.svelte

and it works the way I thought it should, only rendering the test layout.

@ObieMunoz Interesting, that's what I had, and it wasn't working. The named layout was in the same directory as the main layout. I scrapped my project and starting over from scratch I can't reproduce, and it seems to be working as expected.

How can I simulate the same __layout.reset.svelte functionality with this new feature that mostly feels like a downgrade?😐
It seems to be better way how to improve old classic __layout.reset.svelte 😁