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/services/create-service.md
+2 -2
View File
@@ -38,8 +38,8 @@ As the dependency container in Medusa is built on top of [awilix](https://github
There are three lifetime types:
1. `Lifetime.TRANSIENT`: (default for custom services) when used, a new instance of the service is created everytime it is resolved in other resources from the dependency container.
2. `Lifetime.SCOPED`: when used, an instance of the service is created and reused in the scope of the dependency container. So, when the service is resolved in other resources that share that dependency container, the same instance of the service will be returned.
1. `Lifetime.TRANSIENT`: when used, a new instance of the service is created everytime it is resolved in other resources from the dependency container.
2. `Lifetime.SCOPED`: (default for custom services) when used, an instance of the service is created and reused in the scope of the dependency container. So, when the service is resolved in other resources that share that dependency container, the same instance of the service will be returned.
3. `Lifetime.SINGLETON`: (default for core services) when used, the service is always reused, regardless of the scope. An instance of the service is cached in the root container.
You can set the lifetime of your service by setting the `LIFE_TIME` static property: