-
Notifications
You must be signed in to change notification settings - Fork 2
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
add count of vouches with comment #146
Conversation
WalkthroughThe changes made in this pull request enhance the Changes
Possibly related PRs
Suggested reviewers
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
src/server-extension/types.ts (1)
59-61
: Consider adding JSDoc comments for clarity.While the implementation is correct, consider adding documentation to clarify:
- The relationship between
VouchCountByUser.countWithComments
andVouchCountByUserResult.totalWithComments
- What constitutes a "vouch with comments" vs a regular vouch
Example documentation:
+ /** + * Represents the total number of vouches that include comments across all users. + * This is the sum of all VouchCountByUser.countWithComments values. + */ @Field(() => Int) totalWithComments: number = 0;src/server-extension/organization-resolver.ts (2)
119-120
: Consider optimizing the SQL query for better security and performance.While the logic is correct, consider these improvements:
- Use parameterized queries for the comment check to prevent SQL injection
- Use NULLIF for more efficient empty string handling
- SUM(CASE WHEN project_attestation.comment IS NOT NULL AND project_attestation.comment != '' THEN 1 ELSE 0 END) AS count_with_comments + SUM(CASE WHEN NULLIF(project_attestation.comment, '') IS NOT NULL THEN 1 ELSE 0 END) AS count_with_comments
143-154
: Add validation for count values.Consider adding validation to ensure count values are non-negative and handle potential invalid number conversions.
const totalCount = Number(row.total_count); const countWithComments = Number(row.count_with_comments); + if (isNaN(totalCount) || isNaN(countWithComments) || totalCount < 0 || countWithComments < 0) { + throw new Error('Invalid count values in database result'); + } + if (countWithComments > totalCount) { + throw new Error('Comment count cannot exceed total count'); + }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
src/server-extension/organization-resolver.ts
(2 hunks)src/server-extension/types.ts
(1 hunks)
🔇 Additional comments (4)
src/server-extension/types.ts (2)
49-51
: LGTM! Field addition is well-structured.
The new countWithComments
field is properly typed and decorated, with an appropriate default value.
49-51
: Verify resolver implementation for new fields.
Let's ensure the resolver properly populates these new fields.
Also applies to: 59-61
src/server-extension/organization-resolver.ts (2)
Line range hint 119-161
: Implementation looks good overall!
The changes successfully implement the count of vouches with comments while maintaining the existing functionality. The code is well-structured and follows the established patterns. The suggested improvements above are optional optimizations that could enhance robustness and performance.
160-161
: Verify type definitions match the updated return structure.
The return structure has been updated to include totalWithComments
. Please ensure that the corresponding type definitions in types.ts
have been updated accordingly.
✅ Verification successful
Type definitions are correctly aligned with the return structure
The type definition in src/server-extension/types.ts
already includes the totalWithComments
field with the correct type:
export class VouchCountByUserResult {
@Field(() => Int)
totalVouches: number = 0;
@Field(() => Int)
totalWithComments: number = 0;
}
This matches the updated return structure in the resolver.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify type definitions for VouchCountByUserResult
rg -A 5 "VouchCountByUserResult" --type typescript
Length of output: 85
Script:
#!/bin/bash
# Search for type definitions using ripgrep without file type restriction
rg -A 5 "VouchCountByUserResult"
# Also search for interface or type declarations using ast-grep
ast-grep --pattern 'interface VouchCountByUserResult {
$$$
}'
# Search for type alias declarations
ast-grep --pattern 'type VouchCountByUserResult = {
$$$
}'
Length of output: 1967
Summary by CodeRabbit
New Features
Bug Fixes
Documentation