It doesn’t look like there’s an obvious way to change the order of exposed nested instances. Right now the order seems to be based on reverse layer order. It’d be great if the order can be manually adjusted.
8 Likes
I was also looking for a solution for this issue. With regular properties I can see the “draggable” handle. But with a nested instanced there is nothing on hover. I’m wondering if this was the intension from Figma side or it’s just the beta issue?
10 Likes
I don’t get why the order is layer-reverse, it’s very counter intuitive to have the list reversed compared to what you see on the canvas and layer panel.
4 Likes
+1
Here’s a duplicate.
2 Likes
Yes, please! We’ve been leveraging this feature for things like Dropdown Menu options (and the options have props which are nested). The issue with that is, one of the more important nested props, gets shoved all the way to the bottom of the options list of props. Thus, risking the designer/consumer totally missing it without any guidance.
See this example, where we have one unique nested prop for scrolling, that gets pushed too the very bottom:
3 Likes
This is a weird one because I can’t decipher how they’re organized - they’re not by layer order OR reverse layer order for me, they seem just scattershot as to how they’re listed. Feels like there needs to be a way to manually order them OR at least tell us how they’re being organized so we can find a workaround.
1 Like
Still no workaround?
1 Like
I did some testing and it looks like the nested instances properties are ordered based on the order that they appear on the final component, from top to bottom. Changing the position of the component instances in the final component also changes the order of the nested properties.
Knowing this doesn’t help much because for example if you have a text input with a Label, Input Container and Helper text on the bottom, you cant change the position of these instances.
4 Likes
Just wanted to +100 this request. Exposing nested props is what makes Figma super scalable with complex Design System components (e.g., molecules, organisms, templates) and not being able to control the order of these props almost defeat the whole purpose as these props will bounce around based on variants & sub-variants…
Please Figma team!
7 Likes
hey nasgary thanks for investigating. i don’t quite understand what you mean by “order that they appear on the final component”, you mean the order in terms of x y coordinates inside the component?
I mean the physical order that they are in from top to bottom, if you move a nested component to the bottom, the nested component properties also appear on the bottom.
If you look at the screenshot i posted above, you can see that when Comp 1 is on the top of the list, its properties also appears on top in the properties panel.
1 Like
Here to keep this thread alive… I’d love a solution for it
3 Likes
I would also like to be able to put them in between other property types instead having them clustered as “nested instanced”.
Why that? In my case I have multiple toggle switches (true/false) which turn on/off nested components. I would like to group these properties as they belong to each other.
Give us more control please
2 Likes
+1 to this request! (Keepin’ the thread alive)
I’m also deep into complex design systems with sometimes dozens of nested instances. It would significantly improve my workflow to be able to re-order them in the properties manager.
For example, I may have a component layer that is close to the top of the auto-layout frame, therefore it displays at the top of the nested instances list. This component might be seldomly changed from its default state, therefore I’d like to place it at the bottom of the list so I can scroll to the most important items first.
Thanks!
4 Likes
+100, same boat, want to have the feature that let us drag however the order we need to make the nested instances makes most sense based on our components’ scenarios!!
1 Like
Physical order in the layers panel, that is. Helped for me, thanks!
1 Like
I really think this re-pordering function would be a good one to include. So changing the order of nested instance properties but also a very useful addition would be having an option to not expose some properties within that instance.
For example you want the option to turn a layer in that nested instance on/off but you don’t want the text to be changeable even though the master component has both properties. I would like the power to be able to choose which properties are exposed from the nested instance in my final component.
2 Likes
+1 to this, encountered this issue today with a complex component we’re looking to add to the design system. It would really enhanced the utility of nested components to leverage this, some things will rarely be changed, but some will often be changed and atm there’s a lot of properties to go through
3 Likes
Bump! I need this!
+100! I would love to be able to reorder nested instances!