-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking: issues with VSCode extension find-latest-etl-step
#3374
Comments
find-latest-etl-step
find-latest-etl-step
Re-posting from here Nice! I spent some time (actually, too much time...) trying to get searches like "meadow cherry" to work, but apparently, QuickPick doesn’t support fuzzy matching, and I couldn’t find a way to hack it. I think it should be possible to sort the results not just by date, but also by channel. (It took me a while to figure out how to run the extension in development mode. If anyone wants to develop this further and hear about my experience, feel free to reach out.) |
Thanks @Marigold, I also tried making the "meadow cherry" case work, but I also gave up after a while. In any case, just typing "cherry", seeing the list of latest "cherry" steps, and moving or and down to find the meadow step, is better than our current situation (where we hit To me, the main issue with the extension is that it's a bit slow (~2-4 seconds to start). I thought the issue was that it's scanning too many things, even some that should be ignored (like gitignored folders and archives). But I didn't look into it. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Add here any issues you find while using the VSCode extension
find-latest-etl-step
.Known issues
.gitignore
. If you type, e.g.package
you'll see that it lists files from.venv
. For this reason, I had to hardcode ignoring certain folders, likedata/
. But there must be a way to properly take.gitignore
into account (or even better, VSCode configuration, to also ignore archive folders)..gitignore
are excluded, it will be come faster.The text was updated successfully, but these errors were encountered: