Fixed bullet points indentation in Google plugins docstrings.

This commit is contained in:
Fabio Manganiello 2024-01-18 23:58:16 +01:00
parent 6b89ede091
commit c827325e09
Signed by: blacklight
GPG Key ID: D90FBA7F76362774
5 changed files with 90 additions and 90 deletions

View File

@ -26,13 +26,13 @@ class GooglePlugin(Plugin):
4. Click on "Credentials", then "Create credentials" -> "OAuth client ID".
5 Select "Desktop app", enter whichever name you like, and click "Create".
5. Select "Desktop app", enter whichever name you like, and click "Create".
6. Click on the "Download JSON" icon next to your newly created client ID.
Save the JSON file under
``<WORKDIR>/credentials/google/client_secret.json``.
7.1. If you're running the service on a desktop environment, then you
7. If you're running the service on a desktop environment, then you
can just start the application. A browser window will open and
you'll be asked to authorize the application - you may be prompted
with a warning because you are running a personal and potentially
@ -41,7 +41,7 @@ class GooglePlugin(Plugin):
``<WORKDIR>/credentials/google/<list,of,scopes>.json`` and proceed
with the plugin initialization.
7.2. If you're running the service on a headless environment, or you
8. If you're running the service on a headless environment, or you
prefer to manually generate the credentials file before copying to
another machine, you can run the following command:

View File

@ -25,13 +25,13 @@ class GoogleCalendarPlugin(GooglePlugin, CalendarInterface):
4. Click on "Credentials", then "Create credentials" -> "OAuth client ID".
5 Select "Desktop app", enter whichever name you like, and click "Create".
5. Select "Desktop app", enter whichever name you like, and click "Create".
6. Click on the "Download JSON" icon next to your newly created client ID.
Save the JSON file under
``<WORKDIR>/credentials/google/client_secret.json``.
7.1. If you're running the service on a desktop environment, then you
7. If you're running the service on a desktop environment, then you
can just start the application. A browser window will open and
you'll be asked to authorize the application - you may be prompted
with a warning because you are running a personal and potentially
@ -40,7 +40,7 @@ class GoogleCalendarPlugin(GooglePlugin, CalendarInterface):
``<WORKDIR>/credentials/google/<list,of,scopes>.json`` and proceed
with the plugin initialization.
7.2. If you're running the service on a headless environment, or you
8. If you're running the service on a headless environment, or you
prefer to manually generate the credentials file before copying to
another machine, you can run the following command:

View File

@ -25,13 +25,13 @@ class GoogleDrivePlugin(GooglePlugin):
4. Click on "Credentials", then "Create credentials" -> "OAuth client ID".
5 Select "Desktop app", enter whichever name you like, and click "Create".
5. Select "Desktop app", enter whichever name you like, and click "Create".
6. Click on the "Download JSON" icon next to your newly created client ID.
Save the JSON file under
``<WORKDIR>/credentials/google/client_secret.json``.
7.1. If you're running the service on a desktop environment, then you
7. If you're running the service on a desktop environment, then you
can just start the application. A browser window will open and
you'll be asked to authorize the application - you may be prompted
with a warning because you are running a personal and potentially
@ -40,7 +40,7 @@ class GoogleDrivePlugin(GooglePlugin):
``<WORKDIR>/credentials/google/<list,of,scopes>.json`` and proceed
with the plugin initialization.
7.2. If you're running the service on a headless environment, or you
8. If you're running the service on a headless environment, or you
prefer to manually generate the credentials file before copying to
another machine, you can run the following command:

View File

@ -22,13 +22,13 @@ class GoogleFitPlugin(GooglePlugin):
4. Click on "Credentials", then "Create credentials" -> "OAuth client ID".
5 Select "Desktop app", enter whichever name you like, and click "Create".
5. Select "Desktop app", enter whichever name you like, and click "Create".
6. Click on the "Download JSON" icon next to your newly created client ID.
Save the JSON file under
``<WORKDIR>/credentials/google/client_secret.json``.
7.1. If you're running the service on a desktop environment, then you
7. If you're running the service on a desktop environment, then you
can just start the application. A browser window will open and
you'll be asked to authorize the application - you may be prompted
with a warning because you are running a personal and potentially
@ -37,7 +37,7 @@ class GoogleFitPlugin(GooglePlugin):
``<WORKDIR>/credentials/google/<list,of,scopes>.json`` and proceed
with the plugin initialization.
7.2. If you're running the service on a headless environment, or you
8. If you're running the service on a headless environment, or you
prefer to manually generate the credentials file before copying to
another machine, you can run the following command:

View File

@ -34,13 +34,13 @@ class GoogleMailPlugin(GooglePlugin):
4. Click on "Credentials", then "Create credentials" -> "OAuth client ID".
5 Select "Desktop app", enter whichever name you like, and click "Create".
5. Select "Desktop app", enter whichever name you like, and click "Create".
6. Click on the "Download JSON" icon next to your newly created client ID.
Save the JSON file under
``<WORKDIR>/credentials/google/client_secret.json``.
7.1. If you're running the service on a desktop environment, then you
7. If you're running the service on a desktop environment, then you
can just start the application. A browser window will open and
you'll be asked to authorize the application - you may be prompted
with a warning because you are running a personal and potentially
@ -49,7 +49,7 @@ class GoogleMailPlugin(GooglePlugin):
``<WORKDIR>/credentials/google/<list,of,scopes>.json`` and proceed
with the plugin initialization.
7.2. If you're running the service on a headless environment, or you
8. If you're running the service on a headless environment, or you
prefer to manually generate the credentials file before copying to
another machine, you can run the following command: