Make relevant sort work for the tag edit cloud #3

Open
joe wants to merge 2 commits from relevance-sort-fix into master
Collaborator

fixes upstream #820

fixes upstream [#820](https://github.com/shish/shimmie2/issues/820)
joe added 1 commit 2021-12-31 00:34:38 -06:00
butterbutt changed title from Make relevant sort work for the tag edit cloud to WIP: Make relevant sort work for the tag edit cloud 2022-03-15 07:33:38 -05:00
butterbutt requested changes 2022-03-15 07:35:41 -05:00
butterbutt left a comment
Owner

fix typos pls

fix typos pls
@ -81,2 +81,4 @@
return null;
}
$in = ":".implode(", :", array_keys($relevant_tags));;
Owner

lots of extra semicolons in this commit lol

lots of extra semicolons in this commit lol
@ -83,0 +84,4 @@
$in = ":".implode(", :", array_keys($relevant_tags));;
$params = ["tag_min1" => $tags_min, "tag_min2" => $tags_min, "limit" => $max_count];
foreach ($relevant_tags as $key=>$val) {
;
Owner

🤔

🤔
joe marked this conversation as resolved
joe added 1 commit 2022-03-16 17:33:45 -05:00
joe changed title from WIP: Make relevant sort work for the tag edit cloud to Make relevant sort work for the tag edit cloud 2022-03-16 17:34:41 -05:00
joe requested review from butterbutt 2022-03-16 17:34:45 -05:00
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b relevance-sort-fix master
git pull origin relevance-sort-fix

Step 2:

Merge the changes and update on Gitea.
git checkout master
git merge --no-ff relevance-sort-fix
git push origin master
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: butterbutt/shimmie2#3
No description provided.