docs: remove the requirement on is queryable (#8199)

This commit is contained in:
Shahed Nasser authored and GitHub committed 2024-07-21 21:20:24 +02:00
1 parent 8daa4119f0
commit 2f56030101
3 files changed
-34

No files matched your search

@@ -32,31 +32,6 @@ You can then retrieve data across the linked modules, and manage their linked re
--- ---
## Prerequisite: isQueryable Configuration
Before you define a module link, you must enable the `isQueryable` configuration of the module.
For example:
```js
import { HELLO_MODULE } from "./src/modules/hello"
// ...
module.exports = defineConfig({
// ...
modules: {
[HELLO_MODULE]: {
resolve: "./modules/hello",
definition: {
isQueryable: true,
},
},
},
})
```
---
## How to Define a Module Link? ## How to Define a Module Link?
### 1. Create Link File ### 1. Create Link File
@@ -14,12 +14,6 @@ The remote query fetches data across modules. It’s a function registered in th
In your resources, such as API routes or workflows, you can resolve the remote query to fetch data across custom modules and Medusa’s commerce modules. In your resources, such as API routes or workflows, you can resolve the remote query to fetch data across custom modules and Medusa’s commerce modules.
<Note type="check">
- [Enable the isQueryable configuration of the module](../module-links/page.mdx#prerequisite-isqueryable-configuration)
</Note>
--- ---
## Remote Query Example ## Remote Query Example
@@ -144,9 +144,6 @@ module.exports = defineConfig({
modules: { modules: {
marketplaceModuleService: { marketplaceModuleService: {
resolve: "./modules/marketplace", resolve: "./modules/marketplace",
definition: {
isQueryable: true,
},
}, },
}, },
}) })