-
-
Notifications
You must be signed in to change notification settings - Fork 348
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add override
and default
options for cumulative configs
#1692
Comments
I would like to be able to flexibly configure this inheritance. For the first two, you need to use a common complex Layout, for the latter, a simpler layout. Accordingly, I would like to be able to set my own Layout for /create, overwriting the original one. However, there are also reverse situations when you need to specify the Layout for 1 of the many pages, for example: In this case, I have added additional navigation for pages /companies - the ability to inherit previous Layouts is great |
@bighorik Yeah, currently the only way is to do this:
Let me know whether it's a showstopper for you and I'll bump the priority of this ticket. |
I'd love a way to "escape" from a parent layout defined in the renderer. In my app, I have
I have a workaround in renderer's layout, but I don't like it:
Moving the |
@AgentEnder Makes sense. I think this would be nice: // pages/some-page/+config.js
export default {
// Remove all inherited layouts
Layout: null
} |
That could work, currently I divide my PageShell component into MinimumPageShell and the base PageShell as saw above. Ideally I'd be able to set a Layout that is just the MinimumPageShell |
override
and default
override
and default
options for cumulative configs
Basics
Add two new settings
default: boolean | string
andoverride: boolean | string
for controlling cumulative values:Groups
Feedback
If you want this, add a comment below elaborating on why you need this.
The text was updated successfully, but these errors were encountered: