Pierre Verkest
Pierre Verkest
> I find kinda weird this flow. Is it on purpose? > > 1. Payment screen -> Validate > > 2. Enter zip code -> Validate > > 3. Payment...
> I'm thinking... it can probably improved by recalled the method validate method in case user clicked on validate button before collect zipcode as in your gif preview with a...
... and of course you should take care CI complains ;)
I suppose this module is incompatible with project_key, is there a way to tell travis to test them separately ?
> I suppose this module is incompatible with project_key, is there a way to tell travis to test them separately ? Last commit should do the trick waiting from travis...
> > I suppose this module is incompatible with project_key, is there a way to tell travis to test them separately ? > > Last commit should do the trick...
At the time writing it's in a WIP state cf above checklist otherwise reviews and comments are welcome, let me know if you have better idea in naming things !
[thinking out loud] I've the feeling that end users think more about project than analytic account so I thinks it's important to link to project/tasks and more accurate as many...
creating dedicated consumable_project_id/consumable_task_id won't be a good solution or deport complexity to the reporting/analysis parts...
The [latest commit 61e6dda](https://github.com/OCA/project/pull/814/commits/61e6ddaf5b60f1e4a40cb32cefcb83430fb53786) is about fixing unit test base on issue found in project_sequence_task, I'll move it in a dedicated PR if test passed !