`reuse`

This plugin is [REUSE](https://reuse.software/) compliant: it uses SPDX headers to identify licensing information of its source code. More information on the [REUSE](https://reuse.software/) website. You can use the [reuse](https://reuse.readthedocs.io/en/stable/readme.html#) command line tool to help you update headers. The `npm run lint` command will use the `reuse` command to check compliance. Don't forget to add your copyright information in SPDX headers when you modify some code.

change recursively `plugins/node_modules/peertube-plugin-livechat/dist/` files owner to your `peertube` user,

restart your instance.

The minimum required version for Hugo is 0.121.0. It was tested using version 0.132.2.

You can use the `livechat_label` short code to use application strings. See here: [Documentation translation](/peertube-plugin-livechat/contributing/translate/#documentation-translation).

It is possible to prevent a file from beeing translating, using `livechatnotranslation: true` in the Yaml Font Matter section. See here: [Documentation translation](/peertube-plugin-livechat/contributing/translate/#documentation-translation).

Please use the `livechatnotranslation` option for technical documentation. We don't want technical documentation to be translated, to avoid issues because of a wrong translation.

When a new feature is released, you can use the `livechat_version_notice` short code to display an infobox with the version with which the features is available. This short code takes the version number as parameter. Here is an example:

Adding new strings / use translations in the code

If you are working on new features, and need new strings, you can create them directly in Weblate. The english version is mandatory. Start with it.

Each string is linked to a key (for example `use_chat`). Choose an explicit key in english, lower case.

If you have to test new strings without waiting for a Weblate merge, you can modify `languages/*.yml` files, but avoid to commit these changes (to minimize conflict risks).

Use translations in front-end code

Before using a string in front-end, you need to declare a new constant in `client/@types/global.d.ts`. The constant name must:

start with the prefix "LOC_"

use the string key, upper cased

you just have to declare its type, not its value

For example, to use "use_chat", you have to declare:

declare const LOC_USE_CHAT: string