Closed peeradech closed 6 years ago
Yes, confirmed. This is very much related to issue #20 also.
There are two scenarios here in which the code should not explode.
MicroflowConstants:
but nothing after that in the config, which results in MicroflowConstants: null
if you do dump_config
, a.k.a. None in python.MicroflowConstants:
listed at all (if you have no constants at all and strip everything you don't use from the config.Both scenarios do not pop up in our hosting environment, because in the generated files an empty list ends up as an explicit MicroflowConstants: []
in there, never as None. And, the option is always present.
Ehm, as MicroflowConstants: {}
, obviously, since it's a map, not a list.
I put two changes in the develop branch to fix this behaviour. The simple workaround for now is just to add the option as MicroflowConstants: {}
.
Thanks for reporting it. Because of the other issue, #40 there will be a new release soon anyway.
Hi @knorrie
I tried to upgrade m2ee tools to v7.2, I could not start app in the case of not have microflow constants.
Thanks,