Skip to content

added enpoint for users verification status#213

Merged
lovelgeorge99 merged 4 commits intostagingfrom
users-verification-status
May 9, 2025
Merged

added enpoint for users verification status#213
lovelgeorge99 merged 4 commits intostagingfrom
users-verification-status

Conversation

@lovelgeorge99
Copy link
Collaborator

@lovelgeorge99 lovelgeorge99 commented May 8, 2025

Summary by CodeRabbit

  • New Features

    • Introduced a new GraphQL query to retrieve users' verification status, allowing filtering by donation history and verification types.
    • The query returns a list of users and the total count based on selected filters.
  • Tests

    • Added a new test query to validate the user verification status retrieval functionality.

@coderabbitai
Copy link

coderabbitai bot commented May 8, 2025

"""

Walkthrough

A new GraphQL query, getUsersVerificationStatus, was introduced to the user resolver, enabling retrieval of users filtered by donation status and verification flags. Supporting types and enums were added, and a corresponding query string was included in the test queries. No existing logic or control flow was altered.

Changes

File(s) Change Summary
src/resolvers/userResolver.ts Added getUsersVerificationStatus query to UserResolver, introduced UsersData GraphQL object type, and imported DONATION_STATUS enum for filtering.
test/graphqlQueries.ts Added exported GraphQL query string getUsersVerificationStatus for testing the new query.

Sequence Diagram(s)

sequenceDiagram
  participant Client
  participant GraphQLServer
  participant UserResolver
  participant Database

  Client->>GraphQLServer: Query getUsersVerificationStatus(hasDonated, privadoVerified, humanVerified)
  GraphQLServer->>UserResolver: getUsersVerificationStatus(args)
  UserResolver->>Database: Build and execute filtered user query
  Database-->>UserResolver: Return users and count
  UserResolver-->>GraphQLServer: Return UsersData { users, totalCount }
  GraphQLServer-->>Client: Respond with UsersData
Loading

Poem

In the warren of code, a query appears,
To fetch user status, it now volunteers.
With filters for giving, for human, for trust,
The resolver hops swiftly, as all good code must.
Counted and listed, the users are shown—
A field full of carrots, all carefully grown! 🥕
"""

Tip

⚡️ Faster reviews with caching
  • CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ca1bffd and bbd57d7.

📒 Files selected for processing (1)
  • src/resolvers/userResolver.ts (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/resolvers/userResolver.ts
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: test
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

Copy link
Collaborator

@ae2079 ae2079 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good BTW, you can apply changes and merge it to staging and test it on that

}

@Query(_returns => UsersData)
async getUsersVerificationStatus(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to have skipped verification users as well

}

@ObjectType()
class UsersData {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe it is better to have another endpoint too, to get all the users who donated and specify the type of verification of them, and have count of each verification type. it is more related to what Tam requested

@lovelgeorge99 lovelgeorge99 merged commit a6f7833 into staging May 9, 2025
9 checks passed
@lovelgeorge99 lovelgeorge99 deleted the users-verification-status branch May 9, 2025 12:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants