I think this could indeed be a good idea :)
cheers,
Sergeā¦
> On 8 avr. 2016, at 11:39, Thomas Draier wrote:
>
> Hi,
>
> I was thinking of some possible improvements on the condition types, to
> make them more flexible.
> Currently, condition types are defined in unomi
As you already know, I completely agree.
On Fri, Apr 8, 2016 at 11:39 AM Thomas Draier wrote:
> Hi,
>
> I was thinking of some possible improvements on the condition types, to
> make them more flexible.
> Currently, condition types are defined in unomi plugins - they are read
Hi,
I was thinking of some possible improvements on the condition types, to
make them more flexible.
Currently, condition types are defined in unomi plugins - they are read
from a json inside a plugin bundle, and then loaded into memory. Some of
the base conditions rely on actual java code, so it
[
https://issues.apache.org/jira/browse/UNOMI-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Draier resolved UNOMI-22.
Resolution: Fixed
> Filters with "or" condition between session/user conditions do not work
>
Repository: incubator-unomi
Updated Branches:
refs/heads/master 8dfd6ac2c -> 358c4df04
UNOMI-22 : Iterates on sub conditions and check match on session or profile
depending on condition type. Support both "or" and "and" sub conditions
Project:
Thomas Draier created UNOMI-22:
--
Summary: Filters with "or" condition between session/user
conditions do not work
Key: UNOMI-22
URL: https://issues.apache.org/jira/browse/UNOMI-22
Project: Apache Unomi