You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
qml: Use signal based navigation in NodeSettings, don't alias nav elems
In containing pages, everything a page needs should be defined where the
page is declared. Allowing to alias nav elements into a page breaks
the idea of pages being statically defined. The action of aliasing
down nav elements means that the real declaration of a page is not in
its 'filename.qml', but instead where the page is used, meaning a page
can be defined an infinite amount of times in an infinite amount of
ways; we don't want this.
The only reason that we were aliasing down nav elements is that we have
reusable pages for settings and what elements the nav bar will contain
is different depending on whether we are onboarding or not. So, we
should treat that as the navbar for the page has two states, so we
should have logic for these states instead of defining the page in
different locations in different ways.
This state logic is handled by setting a property of onboarding or not,
a follow-up can potentially move this into an appropriate backend object
such as AppMode.
0 commit comments