haven't found an elegant way to
have a ResourceModel with a default *key* if the current key doesn't
exist.
There is a mechanism for a default *string* but it's not sufficient
for us (we want to be able to specialize the key if needed but have an
internationalized default
/0735b05d47b16acf2fd7
https://gist.github.com/tgoetz/0735b05d47b16acf2fd7
Cheers,
-Tom
On 06.11.2014, at 11:53, Guillaume Smet guillaume.s...@gmail.com
wrote:
Hi all,
Maybe we are missing something but we haven't found an elegant way to
have a ResourceModel with a default *key
Hi all,
Maybe we are missing something but we haven't found an elegant way to
have a ResourceModel with a default *key* if the current key doesn't
exist.
There is a mechanism for a default *string* but it's not sufficient
for us (we want to be able to specialize the key if needed but have
an elegant way to
have a ResourceModel with a default *key* if the current key doesn't
exist.
There is a mechanism for a default *string* but it's not sufficient
for us (we want to be able to specialize the key if needed but have an
internationalized default if not).
Suggestions welcome
with a default *key* if the current key doesn't
exist.
There is a mechanism for a default *string* but it's not sufficient
for us (we want to be able to specialize the key if needed but have an
internationalized default if not).
Suggestions welcome!
Thanks.
--
Guillaume