Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

dekarrin
Copy link

This takes the commits introduced in PR #403, which appears to be abandoned by the contributor, and applies the suggestions in that PR and updates the code to fix merge conflicts and broken tests that occurred as a result of master branch diverging from the PR.
It includes the original changes from that PR. In addition, I re-arranged the Dockerfile for server to make caching a little easier (mostly, doing package installs prior to any COPYs to stop 0.5GB images from being generated on every code change), and to add a default BUILDPLATFORM build arg so that it does not need to be explicitly passed via buildargs. Those additions can be pulled out and discussed separately (or wholesale rejected) but I figured I'd keep them in this PR and see if they would be helpful to others.

In addition, this includes the following changes, copied verbatim from PR #403:

Related to #380.

  1. Implements sort:pool for post searches, which will sort the results by the order defined by the pool: named token in the same search query.

  2. Modifies the previous/next post order for the post view if a pool: named token is in the current query.

  3. Adds a grid-based view for the pools list page, showing up to the first three posts in each pool.
    1

  4. Implements pool navigators. They allow navigating to the first/last/next/previous post in each pool the post belongs to. The current pool active in the search query will get bolded/placed at the top.
    2

Ruin0x11 and others added 30 commits May 8, 2021 02:38
…zurubooru into update/Ruin0x11/improve-pools
@po5
Copy link
Collaborator

po5 commented Apr 19, 2024

My fork includes a bunch of styling fixes for pool thumbnails, a bugfix for pool navigation, and a performance optimization for nearby posts serialization.
Filter for commit messages containing pool.

@dekarrin
Copy link
Author

dekarrin commented Apr 19, 2024

Oh, nice! @po5 does that render the changes in this branch redundant? I can close this PR if that's the case, no need to pollute an already dense PR list.

@po5
Copy link
Collaborator

po5 commented Apr 19, 2024

I haven't submitted my pool-related changes yet so feel free to cherry pick.

@Deer-Spangle
Copy link

I haven't submitted my pool-related changes yet so feel free to cherry pick.

@po5 Can you list which commits on your fork are pool related? It looks like you've got over 100 commits of difference over there, and no branch or closed PR over there seems to summarise the changes

)
: uri.formatClientLink("post", ctx.parameters.id);
router.replace(url, ctx.state, false);
console.log(parameters.query);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this console.log() call leftover from testing?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Were the changes to .gitignore here intentionally included or are they specific to your setup?

@kemopup
Copy link

kemopup commented Apr 7, 2025

Any chance on bringing this to Master?

@po5
Copy link
Collaborator

po5 commented Apr 7, 2025

I have a PR at #732 with many fixes and improvements, that is much cleaner and easier to review as well. It doesn't have merge conflicts. It's been running on my instance for a while with no issues. There's still some stuff I want to get done, but nothing blocking a merge.

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.

5 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.