Skip to content
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

Improve tag blocking UI (#1453) #1467

Merged
merged 22 commits into from
Nov 7, 2024
Merged

Conversation

huntertur
Copy link
Contributor

@huntertur huntertur commented Nov 4, 2024

Closes #1453

Before

image

After

image

@charmander
Copy link
Contributor

Thoughts on “Block general and higher” → “Block all ratings”?

@huntertur
Copy link
Contributor Author

I like "block all ratings"; it sounds less cumbersome than "block general and higher".

My one concern is that, in the (admittedly unlikely) event that a rating lower than General is added to the website, tags which were thought to be blocked on all ratings would suddenly no longer be blocked on all tags, since they would start to appear on pre-General content.

I know the prospect of a pre-General rating getting added is very low, but since it sounds like the rating structure may have changed at least once in the past, I bring this up just in case. If you are OK with this, I will make the change, plus the form field name change suggested in the developer chatroom.

Additional concern while reviewing the text further: I notice that elsewhere on the website, ratings seem to usually be referred to with a capital letter; General and Mature and Explicit are often written as such, but they are lowercase here. If I make this change and your suggested change, the list will look like this:

  • Block all ratings
  • Block Mature and higher
  • Block Explicit only

@charmander
Copy link
Contributor

My one concern is that, in the (admittedly unlikely) event that a rating lower than General is added to the website, tags which were thought to be blocked on all ratings would suddenly no longer be blocked on all tags, since they would start to appear on pre-General content.

Yeah, I’m okay with that. On top of that situation being unlikely, I can’t imagine we would do anything in it other than migrate General+ tag filters to also block the new rating.

For what it’s worth, my main concern was that it would stop matching the column. I think keeping General+ in the column is fine, though.

Additional concern while reviewing the text further: I notice that elsewhere on the website, ratings seem to usually be referred to with a capital letter; General and Mature and Explicit are often written as such, but they are lowercase here.

If I make this change and your suggested change, the list will look like this:

  • Block all ratings
  • Block Mature and higher
  • Block Explicit only

This list looks good. (In general, the site overuses title case, and it’s not necessary here, but I have a slight preference for your suggested version.)

weasyl/searchtag.py Outdated Show resolved Hide resolved
weasyl/searchtag.py Outdated Show resolved Hide resolved
weasyl/controllers/settings.py Show resolved Hide resolved
@huntertur huntertur requested a review from charmander November 6, 2024 05:07
@huntertur
Copy link
Contributor Author

Pushed new commits to address code review feedback and retain form compatibility.

weasyl/searchtag.py Outdated Show resolved Hide resolved
@charmander charmander merged commit a3f29e7 into Weasyl:main Nov 7, 2024
4 checks passed
@huntertur huntertur deleted the 1453-tagfilters branch January 1, 2025 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve tag blocking UI
2 participants