-
Notifications
You must be signed in to change notification settings - Fork 30
✨ Add Controller for /me/function-permissions
Endpoint in Functions Domain
#7901
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
base: master
Are you sure you want to change the base?
✨ Add Controller for /me/function-permissions
Endpoint in Functions Domain
#7901
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7901 +/- ##
==========================================
- Coverage 87.88% 87.55% -0.34%
==========================================
Files 1779 1461 -318
Lines 68271 60316 -7955
Branches 1220 476 -744
==========================================
- Hits 60000 52807 -7193
+ Misses 7919 7388 -531
+ Partials 352 121 -231
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
/me/function-permissions
Endpoint in Functions Domain
6e195c5
to
124caa7
Compare
|
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.
Looks good. Thanks.
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.
Merci!!
What do these changes do?
This PR introduces a controller in the
functions
domain that serves theGET /me/function-permissions
endpoint, as required by the front-end in #7888.It leverages the existing service-layer functionality exposed in #7868 via
_functions_service.get_functions_user_api_access_rights
.The implementation follows a minimalistic approach, focusing on fulfilling the immediate client requirements, while being structured to allow easy future extensions (e.g. expanding the response model or improving test coverage).
Related issue/s
How to test
Dev-ops
None