Given we have a plugins with a task_id collided with another task_id in the same plugins.
fpb doesn't complain about it, but it should've.
Even though fuel plugins --install prints errors about duplicated task_ids, the plugin ends up installed.
But it doesn't work, because information from it only partially was inserted into DB.
Exit code of such a faulty installation ends up 0.
Step to reproduce
Install a plugins with duplicated task_id
Expected behavior:
fpb doesn't build a plugin with duplicated task_id
the plugin isn't installed
fuel plugins returns non-zero exit code
Actual behavior:
fpb doesn't complain about duplicated task_id and build plugin
Given we have a plugins with a task_id collided with another task_id in the same plugins.
fpb doesn't complain about it, but it should've.
Even though fuel plugins --install prints errors about duplicated task_ids, the plugin ends up installed.
But it doesn't work, because information from it only partially was inserted into DB.
Exit code of such a faulty installation ends up 0.
Step to reproduce
Install a plugins with duplicated task_id
Expected behavior:
fpb doesn't build a plugin with duplicated task_id
the plugin isn't installed
fuel plugins returns non-zero exit code
Actual behavior:
fpb doesn't complain about duplicated task_id and build plugin
the plugin is installed
fuel plugins returns 0