-
-
Notifications
You must be signed in to change notification settings - Fork 88
Add relay follower query API and refactor types #514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Separate internal storage format from public API types and add helper method to eliminate code duplication in follower data handling. - Add RelayFollowerData for internal KV storage (JSON-LD format) - Rename RelayFollowerEntry to RelayFollower as the main public type - Add parseFollowerData() helper to centralize validation and deserialization - Update isRelayFollower to isRelayFollowerData for storage validation - Keep RelayFollowerData internal (not exported from mod.ts) - Update tests to use new type naming This improves type safety by clearly distinguishing between the storage format (actor: unknown) and the public API format (actor: Actor), while reducing duplication across listFollowers() and getFollower() methods. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Summary of ChangesHello @sij411, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a valuable public API for querying relay followers and significantly improves the type system for better safety and maintainability. The separation of internal storage types (RelayFollowerData) from public API types (RelayFollower) is a well-executed pattern that enhances the developer experience. The new listFollowers and getFollower methods are cleanly implemented, leveraging a shared helper function to avoid code duplication, and are backed by comprehensive tests. I have one suggestion to make the documentation example more robust. Overall, this is an excellent and well-thought-out contribution.
Update JSDoc examples in listFollowers() and getFollower() to show complete working examples including relay creation with createRelay(). Previously the examples referenced 'relay' without showing how to create it, making them incomplete and potentially confusing. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
Codecov Report❌ Patch coverage is
🚀 New features to boost your workflow:
|
- Add public Relay interface with fetch(), listFollowers(), getFollower() - Update BaseRelay to implement Relay interface (marked @internal) - Change createRelay() return type from BaseRelay to Relay - Remove MastodonRelay and LitePubRelay exports from mod.ts - Update README to document interface-based API 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
dahlia
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any more work to add to this pull request? If not, can we take it out of draft?
Summary
Adds public API methods to query relay followers and refactors the type system for better type safety and maintainability.
Related to: #512 (comment)
Changes
New Public API Methods
listFollowers(): AsyncIterableIterator<RelayFollower>- Lists all followers of the relaygetFollower(actorId: string): Promise<RelayFollower | null>- Gets a specific follower by actor IDType System Refactor
Two-type design for clarity:
RelayFollowerData(internal): Storage format with JSON-LD actor data (actor: unknown)RelayFollower(public): API format with validated Actor instances (actor: Actor, includesactorId)Why separate types?
Implementation Details
parseFollowerData()helper to centralize validation and deserializationBenefits