* docs: Added git as in the prerequisites section of the Quickstart Guide
Fixes: #2850
* added divider
Co-authored-by: Shahed Nasser <shahednasser@gmail.com>
* docs: added an upgrade guide for 1.7.1
* docs: added more required changes for the release
* docs: removed link to payment provider docs
* docs: reordered upgrade guides in desc order
* added export to code snippet
* added details about update_request property
* fixed the text
* added link to scheduled jobs docs
* Update Set up your development doc for Medusa CLI section
* Remove auto changes by VS code.
* Update docs/content/tutorial/0-set-up-your-development-environment.mdx
Co-authored-by: Shahed Nasser <shahednasser@gmail.com>
Co-authored-by: Shahed Nasser <shahednasser@gmail.com>
* Add note to run migrations
I think it will be helpful to remind newbies to run migrations after they change their `database_type`. I'm a newbie and today I got stuck for a while because I didn't know I had to run migrations after I changed from `sqlite` to `postgres`.
* Add H3 header "Changing Database Type"
### What
Rename all JSDoc OAS `@schema` and `$ref: #/components/schemas/` from snake_case to PascalCase, `foo_bar -> FooBar`
Extra scope: Remove `x-resourceId` from JSDoc OAS.
### Why
Classes use PascalCase as a convention but the OAS @schemas describing them were using snake_case. OAS code generators tend to use the schema name when generating typed models.
In order to avoid mismatch between source code, the OAS, and the generated client code, it is advised to align OAS @schemas formatting to the classes they represent.
Extra scope: x-resourceId is not a widely used OAS property. It's current usage in our OAS does not provide additional value. Therefore, we recommend to remove it in order to have one less item to maintain.
### How
Good old search & replace. Regex search to further make sure we didn't miss any.
The scope is limited to `@schema` definition and their usage in `$ref: #/components/schemas/`.
### Test
* Ran OAS validator.
* Ran docs build script.
Expect no visible changes to the documentation.
Resolves: CORE-852, CORE-859
**What**
Extract cron job logic from the `EventBusService` to its own service `JobSchedulerService`
**Why**
Preliminary step to extracting the event bus into a module
**Tests**
Tested with a local installation of Medusa
Resolved CORE-918
* docs: Update netlify deploy readme for clarity
It was unlcear why "Gatsby" was mentioned in the env name for the server URL. Also, the code shows precedence given to `MEDUSA_BACKEND_URL` now:
```
__MEDUSA_BACKEND_URL__: JSON.stringify(
env.MEDUSA_BACKEND_URL ||
// Backwards-compat with Gatsby.
env.GATSBY_MEDUSA_BACKEND_URL ||
env.GATSBY_STORE_URL ||
""
),
```
Therefore, this should be indicated in the documentation.
* Update docs/content/deployments/admin/deploying-on-netlify.md
* Update deploying-on-netlify.md
Co-authored-by: Shahed Nasser <shahednasser@gmail.com>
