Skip to content

Conversation

@tolgaozen
Copy link
Member

@tolgaozen tolgaozen commented Nov 22, 2025

Summary by CodeRabbit

  • Documentation

    • Updated badge links in README for release tracking, workflow status, and code quality metrics
  • Tests

    • Added test cases for relation path scenarios, including direct paths, multi-hop connections, and edge cases

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link

coderabbitai bot commented Nov 22, 2025

Warning

Rate limit exceeded

@tolgaozen has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 1 minutes and 23 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 59633fa and 9c1ca12.

📒 Files selected for processing (1)
  • README.md (1 hunks)

Walkthrough

This pull request updates README.md badge links to point to current URLs and adds comprehensive test cases for BuildRelationPathChain functionality in the linked schema test suite, covering direct paths, multi-hop paths, missing paths, and edge cases.

Changes

Cohort / File(s) Summary
Documentation badges
README.md
Updates badge links for Release, Commit Activity, Actions Workflow, Scrutinizer, and Codecov; reintroduces Gurubase AI badge with adjusted placement
Linked schema tests
internal/schema/linked_schema_test.go
Adds new test context "BuildRelationPathChain" with multiple test cases covering direct paths, multi-hop paths, no path scenarios, complex multi-level schemas, and self-referential edge cases

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • README badge URL updates are straightforward cosmetic changes with no risk
  • Test additions require verification of test logic correctness and coverage completeness

Possibly related PRs

Suggested reviewers

  • EgeAytin

Poem

🐰 Badges gleam in rows so bright,
URLs updated, links set right,
Tests now cover paths untold—
Direct, multi-hop, stories bold,
Schema chains both new and tested,
Our little rabbit is quite jested! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title accurately describes the main change: updating README badges, specifically for commit activity and workflow status.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (2)
internal/schema/linked_schema_test.go (2)

1826-2002: Consider splitting this PR into separate concerns.

The PR title indicates "update README badges," but this change adds comprehensive test coverage for BuildRelationPathChain functionality. These are unrelated changes that should ideally be in separate PRs:

  1. One PR for documentation (README badge updates)
  2. Another PR for test additions

That said, the test coverage itself looks solid with good edge case handling (direct paths, multi-hop paths, error cases, self-referential relations, and non-existent entities).


2136-2301: Consider whether manual schema manipulation is necessary.

These tests manually set docDef.References[...] = base.EntityDefinition_REFERENCE_ATTRIBUTE to force specific code paths. While this may be intentional for testing edge cases, note that:

  1. Existing tests (Case 19 at lines 925-970 and Case 20 at lines 972-1023) already test attributes through natural schema compilation
  2. Manual manipulation could be brittle if internal schema structures change
  3. Consider whether these specific code paths can be reached through normal schema compilation

If manual manipulation is truly required for coverage, consider adding a comment explaining why this approach is necessary.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e7bd0e1 and 59633fa.

⛔ Files ignored due to path filters (1)
  • go.work.sum is excluded by !**/*.sum
📒 Files selected for processing (2)
  • README.md (1 hunks)
  • internal/schema/linked_schema_test.go (1 hunks)
🧰 Additional context used
🧬 Code graph analysis (1)
internal/schema/linked_schema_test.go (5)
pkg/dsl/parser/parser.go (1)
  • NewParser (59-78)
pkg/dsl/compiler/compiler.go (1)
  • NewCompiler (25-30)
internal/schema/linked_schema.go (3)
  • NewLinkedGraph (27-31)
  • LinkedEntrance (60-65)
  • AttributeLinkedEntrance (46-46)
internal/schema/schema.go (1)
  • NewSchemaFromEntityAndRuleDefinitions (30-73)
pkg/pb/base/v1/base.pb.go (1)
  • EntityDefinition_REFERENCE_ATTRIBUTE (272-272)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: Test with Coverage
  • GitHub Check: Test with Coverage
🔇 Additional comments (1)
internal/schema/linked_schema_test.go (1)

2004-2134: LGTM! Comprehensive test coverage.

The GetSubjectRelationForPathWalk test cases are well-structured and cover the expected scenarios, including edge cases where entities or relations don't exist.

@codecov
Copy link

codecov bot commented Nov 22, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.23%. Comparing base (e7bd0e1) to head (9c1ca12).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2648      +/-   ##
==========================================
+ Coverage   81.61%   82.23%   +0.61%     
==========================================
  Files          74       74              
  Lines        8132     8132              
==========================================
+ Hits         6637     6687      +50     
+ Misses        978      929      -49     
+ Partials      517      516       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@tolgaozen tolgaozen merged commit 7c933e2 into master Nov 22, 2025
14 checks passed
@tolgaozen tolgaozen deleted the update-readme-and-dependencies branch November 22, 2025 11:36
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