Since there is no official standard for user defined labels/keywords in JMAP it could be a pain if you use different mail clients which handle labels differently. A label defined in ihasmail would not be shown if the other client is coded to use a different label syntax.
For example, Bulwark labels have a "$label:" prefix. While ihasmail names their labels simply "$label" or "label". The JMAP syntax below shows the same label, added twice; once by each client, as they have different approaches to label syntax.
Adding a setting "User defined prefix" to the labels settings would allow a user to make labeling consistent across the clients they use. Could be left empty to keep current method, or could be defined if wanted.
Since there is no official standard for user defined labels/keywords in JMAP it could be a pain if you use different mail clients which handle labels differently. A label defined in ihasmail would not be shown if the other client is coded to use a different label syntax.
For example, Bulwark labels have a "$label:" prefix. While ihasmail names their labels simply "$label" or "label". The JMAP syntax below shows the same label, added twice; once by each client, as they have different approaches to label syntax.
```
"keywords": {
"$label:updates": true, //Bulwark
"updates": true, //ihasmail
"$seen": true
},
```
Adding a setting "User defined prefix" to the labels settings would allow a user to make labeling consistent across the clients they use. Could be left empty to keep current method, or could be defined if wanted.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Since there is no official standard for user defined labels/keywords in JMAP it could be a pain if you use different mail clients which handle labels differently. A label defined in ihasmail would not be shown if the other client is coded to use a different label syntax.
For example, Bulwark labels have a "$label:" prefix. While ihasmail names their labels simply "$label" or "label". The JMAP syntax below shows the same label, added twice; once by each client, as they have different approaches to label syntax.
Adding a setting "User defined prefix" to the labels settings would allow a user to make labeling consistent across the clients they use. Could be left empty to keep current method, or could be defined if wanted.