Structure type definitions to surface Nimbus component props first in autocomplete

[yassinejebli]

When using Nimbus components, the autocomplete lists all props without distinction (custom props get buried under hundreds of inherited Chakra ui/HTML props) making discoverability harder

This matters because ideally we want to encourage devs to reach for the custom component props first rather than defaulting to lower level Chakra customisation. If the custom props are more visible in autocomplete, devs are more likely to use the intended API surface (like onPress vs onClick...)

Question
Would it be feasible to sort/structure the type definitions so that custom component specific props appear before inherited Chakra ui props in autocomplete?

A possible workaround
Using typescript-vscode-plugins with "tsEssentialPlugins.fixSuggestionsSorting": true in vscode settings which respects declaration order

Just opening this for discussion, not a request or a priority.

[jaikamat]

This is a great ask, @yassinejebli. Appreciate the reported workaround from your side. We've created this ticket to address