Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Pagination cursors are accepted with a different sort order or filter

未关闭
#1,111 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go

调研方向

Start by reading TestAPI_CursorOfAnotherQueryListsFromItsPosition from #1109 and compare its asserted behavior with the examples and affected endpoints listed here. The issue leaves open whether to document cursor parameter requirements or reject mismatched queries with a versioned cursor format. Confirm that decision before defining the change; done means the chosen behavior is consistently covered for the listed tenant, event, and attempt lists.

由索引模型根据 Issue 内容生成。

描述

A cursor from one list request can be sent with a different dir or different filters, and the API accepts it. The cursor holds only a position (timestamp and id), so the list continues from that position with the new parameters.

Example: take next from GET /api/v1/events?dir=desc, then request GET /api/v1/events?dir=asc&next=<that cursor>. The response is a 200 with the rows newer than the cursor, which the client has already seen.

GET /api/v1/tenants, GET /api/v1/events, GET /api/v1/attempts and GET /api/v1/tenants/:tenant_id/destinations/:destination_id/attempts all behave this way. The event and attempt lists do so on every log store.

Options:

  • Keep it and document that a cursor is only valid with the parameters of the request that produced it.
  • Reject it with a 400 invalid cursor. The cursor would have to carry a hash of the query parameters, which means a new cursor format version.

TestAPI_CursorOfAnotherQueryListsFromItsPosition (added in #1109) asserts the current behaviour on the event and attempt lists.

主要语言
Go
星标
1.1k
派生
70
平均合并
1 天 3 小时
30 天内合并 PR
50

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

hookdeck/outpost 的其他 Issue

查看 hookdeck/outpost 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。