I discussed this possibility with @tabacitu at some point, and we decided that keys should be managed only by the developers.
If a user changes a key it may break an app or a frontend, and getting it back to work may be difficult if you don't remember the previous key name.
Also, we can change the key on the database, but not in the files, so in reality we would be just creating a new translation [key value] on the database, but keeping the old one from the files. This could led to confusion.
And by the way, creating translations (key > value) is disabled by default but may be enabled by developers in the package config file.
I'll close this one for now, but if someone finds this useful for whatever reason, please re-open 🙌
I discussed this possibility with @tabacitu at some point, and we decided that keys should be managed only by the developers.
If a user changes a key it may break an app or a frontend, and getting it back to work may be difficult if you don't remember the previous key name.
Also, we can change the key on the database, but not in the files, so in reality we would be just creating a new translation [key value] on the database, but keeping the old one from the files. This could led to confusion. And by the way, creating translations (key > value) is disabled by default but may be enabled by developers in the package config file.
I'll close this one for now, but if someone finds this useful for whatever reason, please re-open 🙌