Add localization key to notice messages
- Dominant language
- Python
- Stars
- 72
- Forks
- 84
- Avg merge
- 5h 11m
- Merged PRs (30d)
- 1
Description
Notice messages should also include a localization key so that the client can translate the messages into the correct language. This key should be optional and the client should always be able to fall back to the English `text` field if it receives a notice message with no localization key.
```json
{
"command": "notice",
"style": "info",
"text": "This is some text",
"i18n_key": "some.text.key"
}
```
It probably doesn't make sense to add these keys to the notice messages generated by a `ClientError` as those messages aren't 'supposed to' ever make it to a correctly implemented client. (In practice the protocol isn't quite at the point where that is possible so maybe we want to add this in the future, but lets just start with non `ClientError`s for now.
Contributor guide
Assessment
This issue has not been assessed yet.