Johannes Maron
Johannes Maron
Yes, you are right, the default seems to be the problem. It needs to be added at a later point.
> > Yes, you are right, the default seems to be the problem. It needs to be added at a later point. > > Or it could be made so...
@emihir0 we already implemented this feature. I'll ask someone in my team to share the code here. It would be a cool feature though to have it in the core...
So essentially we have our custom Task model as well as a View mixin. Note that the view mixin requires the view to be saveable, see also http://viewflow-extensions.readthedocs.io/en/latest/views.html ```python class...
@kmmbvnr I understand that, but we can't just not do unit tests. For now we can fall back to manually executing all `HUMAN` tasks. But Testing is really important. We...
I'll look more into it. Should I find any bug, I'll create a PR.
BTW, I found the issue. It's just that you can't execute a task when he's not assigned. All you need is a better exception. And all is fine.
I don't know. It's currently failing whenever Django raises a `VariableDoesNotExist` error. I don't know if it makes sense to add exception to that.
Hm... default is for false values, not for none existing ones. So if your value `foo` is `False` it will not complain. If it does not exist it will.
@jcushman you make a good point, but one could argue the other way, that a context should be consistent, no matter what scenario. Values can be None, but the key...