asyavee/medusa-store
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

chores(medusa): cleanup registrations life time (#3699)

Browse Source
This commit is contained in:
Adrien de Peretti
2023-04-05 12:15:44 +02:00
committed by GitHub
parent 4c268238a4
commit 914d57336b
6 changed files with 28 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/content/development/endpoints/add-middleware.md
+1 -1
View File
@@ -153,7 +153,7 @@ Notice that you have to wrap your usage of the new resource in a try-catch block
If you want to access new registrations in the dependency container within a service, you must set the lifetime of the service either to `Lifetime.SCOPED` or `Lifetime.TRANSIENT`. Services that have a `Lifetime.SINGLETON` lifetime can't access new registrations since they're resolved and cached in the root dependency container beforehand. You can learn more in the [Create Services documentation](../services/create-service.md#service-life-time).
For custom services, no additional action is required as the default lifetime is `Lifetime.TRANSIENT`. However, if you extend a core service, you must change the lifetime since the default lifetime for core services is `Lifetime.SINGLETON`.
For custom services, no additional action is required as the default lifetime is `Lifetime.SCOPED`. However, if you extend a core service, you must change the lifetime since the default lifetime for core services is `Lifetime.SINGLETON`.
For example: