fix: ensure pagination works correctly for flat space hierarchies #1562

Closed
vicr123 wants to merge 2 commits from vicr123/continuwuity:bug/client-hierarchy-pagination-2 into main
First-time contributor

This pull request fixes the hierarchy pagination request for single level hierarchies, by changing the
algorithm used to walk parent/child spaces and rooms. Previously, paginating a space hierarchy would
not work correctly if pagination stopped in the middle of a space.

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
<!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> This pull request fixes the hierarchy pagination request for single level hierarchies, by changing the algorithm used to walk parent/child spaces and rooms. Previously, paginating a space hierarchy would not work correctly if pagination stopped in the middle of a space. <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [X] This pull request targets the `main` branch, and the branch is named something other than `main`. - [X] I have written an appropriate pull request title and my description is clear. - [X] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [X] My contribution follows the [code style][c2], if applicable. - [X] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [X] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [X] My commit messages follow the [commit message format][c1cm] and are descriptive. - [X] I have written a [news fragment][n1] for this PR, if applicable<!--(can be done after hitting open!)-->. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages [n1]: https://towncrier.readthedocs.io/en/stable/tutorial.html#creating-news-fragments
vicr123 force-pushed bug/client-hierarchy-pagination-2 from caf7cc8079
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
to b8261ccbc5
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
2026-03-22 11:08:47 +00:00
Compare
vicr123 force-pushed bug/client-hierarchy-pagination-2 from b8261ccbc5
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
Checks / Prek / Pre-commit & Formatting (pull_request) Has been cancelled
Checks / Prek / Clippy and Cargo Tests (pull_request) Has been cancelled
to 97dc6877c1
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m56s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 16m1s
2026-03-22 11:11:54 +00:00
Compare
nex requested changes 2026-03-27 00:40:16 +00:00
@ -122,0 +125,4 @@
continue;
}
if path.len() == short_room_ids.clone().count()
Owner

You seem to clone() very liberally in this diff - is this necessary? I haven't checked but they look like rather heavy clones

You seem to clone() very liberally in this diff - is this necessary? I haven't checked but they look like rather heavy clones
vicr123 force-pushed bug/client-hierarchy-pagination-2 from 97dc6877c1
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 2m56s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 16m1s
to 5c88c10c7b
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Check Changelog / Check for changelog (pull_request_target) Successful in 11s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m9s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m51s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 16m58s
2026-03-27 04:25:50 +00:00
Compare
Author
First-time contributor

Good call, I've collected the iterator into a vec and borrowed that instead.

Good call, I've collected the iterator into a vec and borrowed that instead.
vicr123 requested review from nex 2026-03-27 04:25:59 +00:00
@ -122,0 +127,4 @@
}
if path.len() == short_room_ids.len()
&& path
Owner

This condition could be split into two ifs with the result of the big stream combinator sequence assigned to a variable for readibility

This condition could be split into two `if`s with the result of the big stream combinator sequence assigned to a variable for readibility
Author
First-time contributor

Done 😃

Done 😃
vicr123 marked this conversation as resolved
@ -122,0 +137,4 @@
.map(|parent_short_room_id| {
short_room_ids.contains(&&parent_short_room_id)
})
.unwrap_or(false)
Owner

This unwrap_or and map combo could be replaced with is_some_and, and frankly the return value of get_shortroomid could be expected since all existing rooms should have a shortroomid

This `unwrap_or` and `map` combo could be replaced with `is_some_and`, and frankly the return value of `get_shortroomid` could be `expect`ed since all existing rooms should have a shortroomid
Author
First-time contributor

Done 😃

Done 😃
vicr123 marked this conversation as resolved
vicr123 force-pushed bug/client-hierarchy-pagination-2 from 5c88c10c7b
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Check Changelog / Check for changelog (pull_request_target) Successful in 11s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m9s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m51s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 16m58s
to a09d667795
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Check Changelog / Check for changelog (pull_request_target) Successful in 10s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m17s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 22m7s
2026-03-29 22:54:33 +00:00
Compare
ginger added this to the (deleted) milestone 2026-04-06 13:06:47 +00:00
Owner

Superseded by #1656.

Superseded by #1656.
ginger closed this pull request 2026-04-14 13:18:44 +00:00
All checks were successful
Documentation / Build and Deploy Documentation (pull_request) Has been skipped
Check Changelog / Check for changelog (pull_request_target) Successful in 10s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 3m17s
Required
Details
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 22m7s
Required
Details

Pull request closed

Sign in to join this conversation.
No reviewers
nex
No milestone
No project
No assignees
3 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
continuwuation/continuwuity!1562
No description provided.