+1 Same Problems! We need the possibility to hide props we don’t want to export for our users.
+1 from me too, very much needed and it would be such a game changer in our DS. Hope this will be possible at some point!
+1, this is really needed.
Same here. The feature is a very good start, but to make it really usable it should be possible to choose which properties from nested components should be exposed / or not in a specific context. Currently it’s everything or nothing. But everything might be too much.
I agree with Harald. It is important to choose which properties from nested components should be exposed / or not in a specific context 🚀
Same. I think it is necessary to implement this improvement, in Sketch this option worked exactly like this
100% this. I had this exact same thought yesterday. I’m also glad to hear that I wasn’t misremembering that this is an option in Sketch.
+1 currently I am not able to use this feature in many cases because it surfaces too many options and only few are needed on the component level.
Managing nested instance in a complex table component makes the table component itself unusable. You approach is simple and fix this issue +1
Would love the option to hide component props from consumers. For instance:
Component A
- Nested component B
- Nested component C
Component A is made up of two nested components, B and C. Components B and C have properties that are adjusted to provide variants of Component A. They’re really just for my use.
But if a designer “clicks in” to Component B, for instance, they can see its props, in the right sidebar (which I’ve used primarily to make those Component A variants). I don’t want them to touch the props for that nested Component B. I’d like to hide them.
I heard rumors that this might be an upcoming feature. Is this true? 🤔
+1 - need capabilities to expose selected properties from within our nested instances. Cannot use this feature without it.
I’m running into this limitation, too. Being able to expose properties from nested instances is the right direction, but I need to be able to selectively expose properties, rather than an all-or-nothing toggle.
Would also be highly interested in this. Would make things much easier for the consumers of our enterprise Design System.
Replying to keep this alive. Our group would love this feature, as something like tabs or lists with nested components becomes such a massive list that they’re not usable.
Agree. It is vital to be able to mark props as private/public or simply specify which of nested components’ props should propagate to their parent.
Keeping the thread alive, +1!
+1 This would make exposing nested instances much more useful for my team as well.
+1 exactly my problem, thank you !
+1 This would be so helpful!
+1, really needed for more complex design systems!