feat: subject filter cursor pagination

[tolgaOzen]

Summary by CodeRabbit

• New Features

  • Updated API documentation to version 1.1.7, reflecting the latest changes.
  • Enhanced subject filtering with sorting functionality for improved result consistency.

• Chores

  • Incremented version number across various documentation and configuration files to maintain version consistency.

[coderabbitai]

Walkthrough

This pull request primarily updates the version number of the Permify API from "v1.1.6" to "v1.1.7" across multiple files, including API documentation and internal configuration files. The updates are strictly semantic, with no changes to the functionality, structure, or error handling of the API. Additionally, the LookupSubject method in the LookupEngine class has been modified to simplify pagination handling, and the subjectFilterDirectRelation method has been enhanced to include sorting functionality.

Changes

File Path	Change Summary
docs/api-reference/apidocs.swagger.json	Version updated from "v1.1.6" to "v1.1.7".
docs/api-reference/openapiv2/apidocs.swagger.json	Version updated from "v1.1.6" to "v1.1.7".
internal/engines/lookup.go	Simplified pagination in LookupSubject method; removed handling for continuous tokens.
internal/engines/subjectFilter.go	Added sorting functionality to pagination in subjectFilterDirectRelation method.
internal/info.go	Version constant updated from "v1.1.6" to "v1.1.7".
proto/base/v1/openapi.proto	Version updated from "v1.1.6" to "v1.1.7".

Possibly related PRs

• build: version info update #1521: Updates the version number in internal/info.go from "v1.0.3" to "v1.0.4", which is related to the versioning changes in the main PR.
• build: version info update #1530: Updates the version number in internal/info.go from "v1.0.4" to "v1.0.5", continuing the versioning updates relevant to the main PR.
• build: version info update #1554: Updates the version number in internal/info.go from "v1.0.5" to "v1.0.6", which is part of the ongoing version updates related to the main PR.
• build: version info update #1597: Updates the version number in internal/info.go from "v1.0.6" to "v1.0.7", aligning with the versioning changes in the main PR.
• build: version info update #1626: Updates the version number in internal/info.go from "v1.1.0" to "v1.1.1", which is directly related to the version updates in the main PR.
• build: version info change #1643: Updates the version number in internal/info.go from "v1.1.1" to "v1.1.2", continuing the versioning updates relevant to the main PR.
• fix(depth-check): correctly handle 'depth not enough' error condition #1707: Updates the version number in internal/info.go from "v1.1.4" to "v1.1.5", which is related to the versioning changes in the main PR.
• refactor: remove unnecessary continuous token handling in subject filter #1708: Modifies the LookupSubject method in internal/engines/lookup.go, which is not directly related to the versioning changes but is part of the same codebase.

🐰 In the meadow, where the bunnies play,
A version update brightens the day.
From "v1.1.6" to "v1.1.7" we hop,
Simplifying code, we’ll never stop!
With sorting and pagination, oh what a delight,
Our API shines, everything feels right! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 3316051 and fe427d0.

📒 Files selected for processing (1)

• internal/engines/subjectFilter.go (3 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• internal/engines/subjectFilter.go

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.