-
Notifications
You must be signed in to change notification settings - Fork 121
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
add filename search as a chip #2213
Conversation
this will make it easier to debug errors from s3 watcher
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! I've wanted this for a while
Great! I wanted this for... like... 3 years. More “debugging” chips I say! |
For the future: this (and maybe all chips) should accept wildcards... |
Interesting. Do you have an example where this should apply? |
I try not to let me sick mind wonder where there are no examples. As with all things search/filter, this applies in the same way to Grid, Open Explorer, Bubbles (@currysoup 👋) and all else. If I would like to appear just a little bit facetious, I would say it wouldn’t exactly hurt to have it in dotcom too. Applies to fields AND to values. (Baby-syntax for wildcards/broken regex/stupid mix. I don’t care much for which is chosen as long as there is an easily accessible help where I will be learning it all over again every single time.)
All this combined with filters showing no. of hits next to properties (and an extra free-text filter for entering the property you’re interested in*) should make most librarians blush. *to explain, imagine:
I could go on. How useful any of that would be? How popular? I’m not paid to care seriously for such questions. Luckily. |
Anecdata-lly, out of all weak signals of photoshoots, filenames are a surprisingly strong one (just look for matching strings where only the numbers differ). |
This will make it easier to debug errors from s3 watcher.