-
Notifications
You must be signed in to change notification settings - Fork 497
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
AO3-6541 Update Works search and filters to use "Creator" instead of "Author/Artist" #4553
Open
forceofcalm
wants to merge
16
commits into
otwcode:master
Choose a base branch
from
forceofcalm:AO3-6541
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 2 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
5e2410a
inital push of author/artist -> creator text change on search forms
forceofcalm b94b12f
hound fixes: switching single quotes to double quotes
forceofcalm 6489f2f
hound fixes: marking word arrays
forceofcalm db8d75b
fix for array that was not a word array
forceofcalm 8e266e9
updated authors_to_sort_on to creator_to_sort_on plus some hound fixes
forceofcalm e899e8d
whoops!
forceofcalm 95fb510
whoops! pt 2. somehow changed creators member to creator, reverted
forceofcalm bd076f9
merge conflicts
forceofcalm 7b6e784
saiting the hound
forceofcalm 213543a
linter changes
forceofcalm 5af7df7
more linter errors
forceofcalm 5419914
fingers crossed
forceofcalm 53c9403
reverting changes; remaining frontend change
forceofcalm 9fe9eca
missed one
forceofcalm b72e6a7
i know how to do translations now
forceofcalm f4c5b46
jk
forceofcalm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Wondering if I should actually do this, since we have instances of whitespace in "Date Posted", "Date Updated", etc. so it wouldn't be consistent on each? I'm a Ruby noob, welcome to other thoughts here.
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.
I personally don't love the mix of array styles, but we do it in the tag_search_form, so I guess it makes sense to do it here as well.