-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[backend] Improve config restrictions / visibility for batch rel loading #6473
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6473 +/- ##
==========================================
- Coverage 67.65% 67.65% -0.01%
==========================================
Files 532 532
Lines 65001 65017 +16
Branches 5434 5437 +3
==========================================
+ Hits 43979 43988 +9
- Misses 21022 21029 +7 ☔ View full report in Codecov by Sentry. |
return resolve; | ||
} | ||
// If access is not possible, return a restricted entity | ||
return { id: resolve.internal_id, name: 'Restricted', entity_type: resolve.entity_type }; |
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.
Would it be possible for a given entity_type to NOT have a name
attribute, leading to an impossible object schema-wise ? an opinion for instance.
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.
I have the same issue in my PR #6323
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.
As discussed, if you're confident it concerns only entities with names, let's go for it as it would not be disruptive for the frontend side.
Different improvements out of the milestone.