Skip to content

Commit d00b129

Browse files
FalkWolskygitbook-bot
authored andcommitted
GITBOOK-195: No subject
1 parent ccf0db1 commit d00b129

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/lowcoder-extension/opensource-contribution/develop-data-source-plugins.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -243,7 +243,7 @@ const i18n = new I18n({ zh, en }, languages);
243243

244244
## Auto-generate plugin code based on Open API
245245

246-
If the data source you're going to develop as a plugin provides an [Open API Spec](https://en.wikipedia.org/wiki/OpenAPI\_Specification) definition file, then its plugin code can be quickly generated.
246+
If the data source you're going to develop as a plugin provides an [Open API Spec](https://en.wikipedia.org/wiki/OpenAPI_Specification) definition file, then its plugin code can be quickly generated.
247247

248248
Below is an example of generating Jira plugin code.
249249

@@ -268,7 +268,7 @@ Due to various reasons, the generated plugin code needs to be correctly validate
268268

269269
## Testing
270270

271-
Necessary testing should be done before publishing the plugin. Testing a data source plugin requires a backend environment. You can start a local environment by following the documentation [Start a local backend server](https://github.com/Lowcoder-dev/Lowcoder/tree/develop/client#readme) and test the data source plugin in following aspects:
271+
Necessary testing should be done before publishing the plugin. Testing a data source plugin requires a backend environment. You can start a local environment by following the documentation [Start a local backend server](https://github.com/lowcoder-org/lowcoder/tree/main/server/api-service) and test the data source plugin in following aspects:
272272

273273
1. Make sure the data source plugin has been added to the plugin list in the file `src/plugins/index.ts`.
274274
2. Start the node-service server in the `node-service` directory by executing `yarn dev`.

0 commit comments

Comments
 (0)