2
95%
master: 95%

Ran 01 Jul 2015 04:53PM UTC

Files 9

Run time 1s

Badge

Embed ▾

Committed 01 Jul 2015 04:45PM UTC coverage: 90.036% (+9.1%) from 80.961%

Job # 295.2

Build Type

push

travis-ci

Committed by

xethorn

Commit Message

Add support for manual deciders.

Some flows are more complex than others. For instance: some activities can
be scheduled based on a condition in the context. Being able to (easily)
write the decider has a lot of advantages.

For this: in your flow, you need to define a decider method that takes a
`schedule` param. To call an activity, all you have to do is to call
`schedule`, provide an immutable id, the activity and a list (if necessary)
of requirements. Example:

```python
def decider(schedule):
    activity_1 = schedule(
        'activity_1', test_activity_1)
    activity_2 = schedule(
        'activity_2', test_activity_2, requires=[activity_1])

    for i in range(3):
        activity_3 = schedule(
            'activity-3.{}'.format(i), test_activity_3, requires=[activity_2])

        if activity_3.ready and activity_2.result.get('4') == 4:
            last_activity = schedule(
                'last_activity.{}'.format(i), test_activity_last,
                input=dict(the='end'))
```

Remember: the decider is called anytime you have an event has occurred. So this
method should only be focused on scheduling (and nothing else).

@rantonmattei

Coverage Stats

506 of 562 relevant lines covered (90.04%)

0.9 hits per line

xethorn / garcon / 295 / 2
95%
master: 95%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 295.2

xethorn / garcon / 295 / 2 95% master: 95%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 295.2

xethorn / garcon / 295 / 2
95%
master: 95%

README BADGES
x