self-hosted/joplin
1
0
Fork 0
mirror of https://github.com/laurent22/joplin.git synced 2026-06-18 20:16:34 +02:00
Code Issues Releases Activity

Doc: Fixing typos (#5644)

Browse Source
This commit is contained in:
Andreas Deininger
2021-10-30 10:45:02 +01:00
committed by GitHub
parent f7a18bac2a
commit 6393996694
14 changed files with 31 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
readme/api/get_started/plugins.md
+2 -2
View File
@@ -17,9 +17,9 @@ Then, in the directory where you plan to develop the plugin, run:
yo joplin
This will generate the basic scafolding of the plugin. At the root of it, there are a number of configuration files which you normally won't need to change. Then the `src/` directory will contain your code. By default, the project uses TypeScript, but you are free to use plain JavaScript too - eventually the project is compiled to plain JS in any case.
This will generate the basic scaffolding of the plugin. At the root of it, there are a number of configuration files which you normally won't need to change. Then the `src/` directory will contain your code. By default, the project uses TypeScript, but you are free to use plain JavaScript too - eventually the project is compiled to plain JS in any case.
The `src/` directory also contains a [manifest.json](https://github.com/laurent22/joplin/blob/dev/readme/api/references/plugin_manifest.md) file, which contains the various information about the plugin that was set in the inital generation of the scaffolding, such as its name, homepage URL, etc. You can edit this at any time, but editing it after it has been published may cause users to have to download it again.
The `src/` directory also contains a [manifest.json](https://github.com/laurent22/joplin/blob/dev/readme/api/references/plugin_manifest.md) file, which contains the various information about the plugin that was set in the initial generation of the scaffolding, such as its name, homepage URL, etc. You can edit this at any time, but editing it after it has been published may cause users to have to download it again.
## Setup Source Control
readme/api/references/rest_api.md
+2 -2
View File
@@ -81,7 +81,7 @@ Then you will resume fetching the results using this query:
curl http://localhost:41184/notes?order_by=updated_time&order_dir=ASC&limit=10&page=2
Eventually you will get some results that do not contain an "has_more" paramater, at which point you will have retrieved all the results
Eventually you will get some results that do not contain an "has_more" parameter, at which point you will have retrieved all the results
As an example the pseudo-code below could be used to fetch all the notes:
@@ -126,7 +126,7 @@ To retrieve all the tags that start with `project-`: **GET /search?query=project
# Item type IDs
Item type IDs might be refered to in certain object you will retrieve from the API. This is the correspondance between name and ID:
Item type IDs might be referred to in certain object you will retrieve from the API. This is the correspondence between name and ID:
Name | Value
---- | -----