Daniel Roe
Daniel Roe
sometimes changing a nested route should scroll to the top - it depends. maybe we can track the nested element and scroll _it_ to the top
if there is scrollable content on the nested page
exactly. that's what I meant by this: > maybe we can track the nested element and scroll it to the top
yes, this issue is still open because it shouldn't be necessary to scroll a parent page if only the child page is rerendering.
unlikely. but bug fixes aren't tied (or relevant) to a major version. any fix will be backported to v3
setting `scrollToTop: false` in a child page disables it for all components that render that route. (Route meta is merged into a single meta object that applies to the route,...
do I understand correctly - you want a layer to be able to import something that is located in the 'consuming' project (ie it is not in the layer?)
yes, that's expected. what happens when you use named layer aliases?
layers do have/support a shared folder
let's track upstream (hopefully resolved in nitro v3!)