diff options
| author | dakkar <dakkar@thenautilus.net> | 2024-08-16 14:41:04 +0100 |
|---|---|---|
| committer | dakkar <dakkar@thenautilus.net> | 2024-08-16 14:41:04 +0100 |
| commit | 90e9480b92411373f4efba9884208a924a4d9fe8 (patch) | |
| tree | d9a00f737c5588facaf6ec0652b176f4e7bfdd76 /packages/backend/src/server/api/openapi | |
| parent | merge: i18n: add missing Japanese translations, fixes #613 (!595) (diff) | |
| download | sharkey-90e9480b92411373f4efba9884208a924a4d9fe8.tar.gz sharkey-90e9480b92411373f4efba9884208a924a4d9fe8.tar.bz2 sharkey-90e9480b92411373f4efba9884208a924a4d9fe8.zip | |
fix `offestMode` in `MkPagination` - fixes #622
3f73251df5967ad47f61f1a6541f9d5ff6563f72 reworked the way `offsetMode`
is handled, to allow reactive `ComputedRef<boolean>` in addition to a
simple `boolean`, so that custom emoji search could easily switch
between the faster `sinceId`/`untilId` pagination and the slower
`offset` as needed.
Or it would have, if I had written the correct expression! I wrote
`props.offsetMode` instead of `props.pagination.offsetMode`, so it was
always `false`
I have *no idea* how I didn't notice, I swear I tested it ☹
Anyway, factoring out the nested ternaries makes the whole thing
clearer and less prone to mistakes. And I have tested it, this time.
Diffstat (limited to 'packages/backend/src/server/api/openapi')
0 files changed, 0 insertions, 0 deletions