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
Feature Request: Some form of path auto-completion
The more I play with datatree, the more I realize the huge potential of this package. Amazing work @TomNicholas.
I have been using dt for CMIP6 analysis and one of the things that is still fairly slow for me is to navigate into different specific leaves of the tree. Having some sort of incremental auto-complete of the path like this:
similar to what happens in the bash shell with tab completion would be an absolute killer feature. Most users already know how to navigate this (from their terminal). For massive trees this would speed up the workflow tremendously.
On the other hand I have no idea how complex this is to implement. Just wanted to suggest this feature.
The text was updated successfully, but these errors were encountered:
To clarify what's said in xarray-contrib/datatree#189 - autocompletion is already implemented, what is not implemented is autocompletion of any path containing a . or ../.
In other words this issue now tracks this ToDo in the code:
What is your issue?
Copying over from xarray-contrib/datatree#189
Feature Request: Some form of path auto-completion
The more I play with datatree, the more I realize the huge potential of this package. Amazing work @TomNicholas.
I have been using dt for CMIP6 analysis and one of the things that is still fairly slow for me is to navigate into different specific leaves of the tree. Having some sort of incremental auto-complete of the path like this:
similar to what happens in the bash shell with tab completion would be an absolute killer feature. Most users already know how to navigate this (from their terminal). For massive trees this would speed up the workflow tremendously.
On the other hand I have no idea how complex this is to implement. Just wanted to suggest this feature.
The text was updated successfully, but these errors were encountered: