chore: clean files using pre-commit
This commit is contained in:
parent
f4dbc584e1
commit
0061e82ecd
81 changed files with 137 additions and 128 deletions
|
|
@ -15,4 +15,4 @@ authentication
|
|||
rate_limit
|
||||
subsonic
|
||||
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -147,4 +147,4 @@ You can check the full list of options by passing the `-h` flag:
|
|||
|
||||
```sh
|
||||
docker-compose -f dev.yml run --rm api pytest -h
|
||||
```
|
||||
```
|
||||
|
|
|
|||
|
|
@ -210,7 +210,7 @@ In this example, **Alice** notifies **Bob** that she's undoing her follow.
|
|||
See [the `Audio` object reference](#audio) for details on the object's structure.
|
||||
```
|
||||
|
||||
When Funkwhale receives a `Create` activity with an [`Audio` object](#audio), it persists a local upload in the database. It then associates the upload to related library and track information. If no track matches the audio metadata, Funkwhale creates on using the `metadata` attribute in the object.
|
||||
When Funkwhale receives a `Create` activity with an [`Audio` object](#audio), it persists a local upload in the database. It then associates the upload to related library and track information. If no track matches the audio metadata, Funkwhale creates on using the `metadata` attribute in the object.
|
||||
|
||||
#### Checks
|
||||
|
||||
|
|
@ -363,7 +363,7 @@ In this example, **Bob** deletes three audio objects in a library and notifies t
|
|||
|
||||
### Artist
|
||||
|
||||
An `Artist` is a custom object used to store musical artist and podcast creator information.
|
||||
An `Artist` is a custom object used to store musical artist and podcast creator information.
|
||||
|
||||
#### Properties
|
||||
|
||||
|
|
@ -404,7 +404,7 @@ An `Artist` is a custom object used to store musical artist and podcast creator
|
|||
|
||||
### Album
|
||||
|
||||
An `Album` is a custom object used to store album and podcast series information.
|
||||
An `Album` is a custom object used to store album and podcast series information.
|
||||
|
||||
#### Properties
|
||||
|
||||
|
|
|
|||
|
|
@ -100,16 +100,16 @@ Your `plugins` should include the following information:
|
|||
* - `name`
|
||||
- String
|
||||
- The name of your plugin, used in the `.env` file
|
||||
* - `label`
|
||||
* - `label`
|
||||
- String
|
||||
- The readable label that appears in the Funkwhale frontend
|
||||
* - `description`
|
||||
* - `description`
|
||||
- String
|
||||
- A meaningful description of your plugin and what it does
|
||||
* - `version`
|
||||
* - `version`
|
||||
- String
|
||||
- The version number of your plugin
|
||||
* - `user`
|
||||
* - `user`
|
||||
- Boolean
|
||||
- Whether the plugin is a **user-level** plugin or a **pod-level** plugin. See [scopes](#scopes) for more information
|
||||
* - `conf`
|
||||
|
|
@ -197,4 +197,4 @@ Here is an example of how the above plugin works:
|
|||
1. User "Harry" enables the plugin
|
||||
2. "Harry" changes the greeting to "You're a wizard"
|
||||
3. "Harry" visits the `/greeting` endpoint in their browser
|
||||
4. The browser returns the message "You're a wizard Harry"
|
||||
4. The browser returns the message "You're a wizard Harry"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue