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
damien-thiesson
changed the title
Medusa v2 Docs: Issue in 1. Introduction - Medusa v2 Docs
Medusa v2 Docs: Issue in module creation example
Sep 21, 2024
damien-thiesson
changed the title
Medusa v2 Docs: Issue in module creation example
Medusa v2 Docs: Typo in module creation example + clarification
Sep 21, 2024
…cs (#9222)
### What
This PR addresses an issue in the Medusa v2 documentation regarding the module creation example. The import paths were corrected to reflect the proper directory structure, ensuring clarity for users.
Closes#9220
### Why
The previous documentation contained incorrect import paths that could lead to confusion for users attempting to create and configure modules. Clarifying the structure aims to prevent similar issues for future users.
### How
- Updated the import statements in the documentation to go two levels up instead of three.
- Added clarification in the `medusa-config.js` example to indicate that the `modules` node should be a part of `projectConfig`.
### Testing
While documentation changes do not require formal testing, I reviewed the updated paths and descriptions against the current code structure to ensure accuracy and clarity.
### Note
This is my first contribution to an open source project, and I'm excited to contribute to the Medusa community!
What Medusa version and documentation are you using?
v2
Preliminary Checks
Issue Summary
In https://docs.medusajs.com/v2/basics/modules-and-services#test-the-module, the example provided contains
It should only go two levels up:
Also for clarity, in the example of
medusa-config.js
(https://docs.medusajs.com/v2/basics/modules-and-services#3-add-module-to-configurations), you probably want to clarify how the structure is altered. I myself made the mistake of putting themodules
node underprojectConfig
and got stuck for a while. Current version in the documentation:Suggested change to clarify and avoid other people doing the same mistake:
How can this issue be resolved?
Are you interested in working on this issue?
The text was updated successfully, but these errors were encountered: