You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am currently studying medusa 2.0. While reviewing the documentation on modules, my attention was drawn to the fact that the module's main service is the only resource defined as a class. Creating other resources is shown as exporting specific functions, configs etc. At first glance this seems strange to me, as it differs from the standard that the rest of the examples presents. It seems to me that I may be missing an important element. Is there a specific reason for breaking out of the convention that seems to be present in the rest of the code? Something such important that it makes it impossible to go with "convention" and forces to settle on classes?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I am currently studying medusa 2.0. While reviewing the documentation on modules, my attention was drawn to the fact that the module's main service is the only resource defined as a class. Creating other resources is shown as exporting specific functions, configs etc. At first glance this seems strange to me, as it differs from the standard that the rest of the examples presents. It seems to me that I may be missing an important element. Is there a specific reason for breaking out of the convention that seems to be present in the rest of the code? Something such important that it makes it impossible to go with "convention" and forces to settle on classes?
Beta Was this translation helpful? Give feedback.
All reactions