Topic: [Feature] Search both tags in requests

Posted under Site Bug Reports & Feature Requests

Overview Allow users to search both the from and to fields on the alias and implication lists
Usefulness With wildcards, you can check to see if multiple tags including the same string are all being moved to the same point, or a point also sharing the same string. For example, *art* invalid_tag would find all art related tags that were aliased to invalid tag, or what tags invalid_tag implies that include the string art.
Effected pages Alias list and implications list

This is actually already possible, there's just not an intuitive way of doing it using the form provided on the page right now:

This should provide what you want: https://e621.net/tag_aliases?search[consequent_name]=invalid_tag&search[name_matches]=*art*

Unfortunately wildcards only seem to work with name_matches and not antecedent_name or consequent_name.

name_matches matches both fields so it can produce undesirable effects if the pattern you're searching for (in this example *tag*) also occurs in the consequent_name.

Updated

Since this is already possible anyways I don't see why it shouldn't be exposed in the UI. I can also make wildcards work while I'm at it.

earlopain said:
Since this is already possible anyways I don't see why it shouldn't be exposed in the UI. I can also make wildcards work while I'm at it.

Since you're looking at it, is there any reason you can't search aliases/implications by who requested them anymore? The ability was there before the codebase was changed, and BURs can be filtered by creator.

It probably just got lost, I don't see a reason why that shouldn't be searchable. Sure, I can add it.

bitWolfy

Former Staff

earlopain said:
It probably just got lost, I don't see a reason why that shouldn't be searchable. Sure, I can add it.

What about searching for those who approved them?
My vanity demands it.

... we are just piling on feature requests on you, aren't we?

bitwolfy said:
What about searching for those who approved them?
My vanity demands it.

... we are just piling on feature requests on you, aren't we?

Can I ask for a "Mine" button while we're at it then? Just defaults to a search that's blank aside from the requester being your own account.

Mostly done, but adding wildcard searches to the two fields clashes with how it is done right now since you can provide multiple space-separated tags to search for them all, and that doesn't work with wildcards. Changing that would break existing behaviour for potential api consumers. I also don't want to add a new search parameter just for wildcard searches, so it's going to stay as is. You will however be able to provide them comma-separated, like all the other fields supporting that do.

furrin_gok said:
Can I ask for a "Mine" button while we're at it then? Just defaults to a search that's blank aside from the requester being your own account.

I added the creator to both the index listing and search options, that should about do it.

Stuff is not live yet, once it is I will of course add it to the changelog.

  • 1