-
Notifications
You must be signed in to change notification settings - Fork 36
♻️ Refactor simcore_service_catalog
: Apply Layered Architecture and Initialization Cleanup
#7491
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
♻️ Refactor simcore_service_catalog
: Apply Layered Architecture and Initialization Cleanup
#7491
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7491 +/- ##
==========================================
- Coverage 87.44% 87.32% -0.13%
==========================================
Files 1741 1566 -175
Lines 67375 63372 -4003
Branches 1142 908 -234
==========================================
- Hits 58919 55339 -3580
+ Misses 8138 7774 -364
+ Partials 318 259 -59
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
5559d74
to
71052a2
Compare
simcore_service_catalog
: Apply Layered Architecture and Initialization Cleanup
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.
Copilot reviewed 66 out of 66 changed files in this pull request and generated no comments.
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.
👍 nice
It's a matter of style, but as you know, I'm a bigger proponent of organizing code by feature or domain (vertical slicing) rather than by type (horizontal slicing). Each domain or feature folder contains everything it needs to function :P
but anyway this organization on controller - service - repository pattern is very very good! thank you Just for reference:
|
services.py # unfortunately this is the name of the resource we handle in the catalog. Any suggestions? --> |
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.
not sure I get the singular or plural of the folders.
I suggest using simcore_services.py
or user_services.py
services/catalog/src/simcore_service_catalog/api/_dependencies/database.py
Outdated
Show resolved
Hide resolved
services/catalog/src/simcore_service_catalog/api/_dependencies/director.py
Outdated
Show resolved
Hide resolved
services/catalog/src/simcore_service_catalog/api/rest/_services_access_rights.py
Outdated
Show resolved
Hide resolved
services/catalog/src/simcore_service_catalog/api/rest/_services_extras.py
Outdated
Show resolved
Hide resolved
services/catalog/src/simcore_service_catalog/api/rest/_services_resources.py
Outdated
Show resolved
Hide resolved
services/catalog/src/simcore_service_catalog/core/background_tasks.py
Outdated
Show resolved
Hide resolved
services/catalog/src/simcore_service_catalog/service/services.py
Outdated
Show resolved
Hide resolved
@mergify queue |
🟠 Waiting for conditions to match
|
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.
Thanks a lot
…cated _dependencies module
…ated repository modules
…rove logging with log_catch
…with repository_lifespan for improved clarity
…led to background_task_lifespan_disabled for improved clarity
… repository_lifespan_manager for improved clarity
…or published templates
21d13a5
to
12cc2d3
Compare
|
What do these changes do?
This PR refactors the
simcore_service_catalog
service to align with a cleaner layered architecture (controller–service–repository). Key improvements include:A commented version of the updated service skeleton is included for clarity.
Related issue/s
How to test
Dev-ops
None