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
Running bit list with wildcards would list only components matching the wildcard.
Actual Behavior
Not supported.
Implementation details
currently bit list shows the local scope components and bit list remote-scope shows the remote components. So, we can't use the main argument for the wildcard as it is used for showing remote-scope.
My suggestion is to add a new flag --namespace <string>, which will accept wildcards.
E.g. bit list --namespace utils/* shows all components of utils namespace in the local scope. bit list remote-scope --namespace ui/* shows all components of ui namespace in the remote scope.
Most of the work already implemented as part of #1681.
It's undocumented, but currently, running bit list scope/ui/* for example, shows only ui collection of the remote-scope. I'd like to extend the functionality to work for the local scope as well, and for this, we'll need a new flag.
Expected Behavior
Running bit list with wildcards would list only components matching the wildcard.
Actual Behavior
Not supported.
Implementation details
currently
bit list
shows the local scope components andbit list remote-scope
shows the remote components. So, we can't use the main argument for the wildcard as it is used for showing remote-scope.My suggestion is to add a new flag
--namespace <string>
, which will accept wildcards.E.g.
bit list --namespace utils/*
shows all components ofutils
namespace in the local scope.bit list remote-scope --namespace ui/*
shows all components ofui
namespace in the remote scope.Most of the work already implemented as part of #1681.
It's undocumented, but currently, running
bit list scope/ui/*
for example, shows only ui collection of the remote-scope. I'd like to extend the functionality to work for the local scope as well, and for this, we'll need a new flag.@GiladShoham , @itaymendel , please let me know if you're good with the suggestion above.
The text was updated successfully, but these errors were encountered: