Hi,
would it be possible to add a SerializerInterface + implementation which does the exact opposite of the DeserializerInterface?
Or is something like that already implemented? Maybe a __toString function for the RuleGroupInterface would also be suitable.
Hi,
would it be possible to add a SerializerInterface + implementation which does the exact opposite of the DeserializerInterface?
Or is something like that already implemented? Maybe a __toString function for the RuleGroupInterface would also be suitable.