Skip to content

ReBAC: set strategy for checking relations#100

Merged
uatuko merged 14 commits intomainfrom
feature/rebac-set-strategy
May 16, 2024
Merged

ReBAC: set strategy for checking relations#100
uatuko merged 14 commits intomainfrom
feature/rebac-set-strategy

Conversation

@uatuko
Copy link
Copy Markdown
Owner

@uatuko uatuko commented May 15, 2024

Introduce set strategy for checking relations, which uses a set intersection algorithm to derive relations between entities if a direct relation cannot be found.

💡 Refer to tests for a visual example on how the set strategy works.

@uatuko uatuko mentioned this pull request May 15, 2024
14 tasks
@codecov
Copy link
Copy Markdown

codecov bot commented May 15, 2024

Codecov Report

Attention: Patch coverage is 94.20290% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 93.05%. Comparing base (d49eaa4) to head (a22f660).

Files Patch % Lines
src/svc/relations.cpp 95.58% 0 Missing and 3 partials ⚠️
src/db/tuples.h 0.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #100      +/-   ##
==========================================
+ Coverage   92.85%   93.05%   +0.19%     
==========================================
  Files          18       18              
  Lines        1148     1209      +61     
  Branches      133      146      +13     
==========================================
+ Hits         1066     1125      +59     
  Misses         62       62              
- Partials       20       22       +2     

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

@uatuko uatuko marked this pull request as ready for review May 16, 2024 11:03
@uatuko uatuko merged commit 0eb3099 into main May 16, 2024
@uatuko uatuko deleted the feature/rebac-set-strategy branch May 16, 2024 19:37
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