|
|
|
[
Permlink
| « Hide
]
Wil Sinclair - 09/Jun/08 01:53 PM
If we'd like to address this, maybe we can coordinate with Thomas on it?
I assigned it to me due to Wil's last comment.
Has to be discussed with the dev-team as it would be a BC break. I propose to make a sort of standard for keys.
A working solution would be to name the keys like:
For example: and so on. I think you get an idea. Assigned to Matthew after a discussion in #zftalk
Issue has been postponed until 2.0 after a discussion with the dev-team.
Reason is that the fix for this issue would be a BC break. Yeah, but i think dev-team could solve this right now, solving the BC issue just by keeping both old and new message keys and discouraging using of old message keys, and then removing them in 2.0.
This has already been discussed in past.
Adding old and new messages raises unsolvable problems because it's not possible to have two messages available for the same error.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||