-
Bug
-
Resolution: Duplicate
-
Minor
-
fuse-7.x-GA
(Migrated from https://github.com/syndesisio/syndesis/issues/6122)
Author: Martin Muzikar
Assignees: Zoran Regvart,
This is a...
[pre][code]
[ ] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report [!-- Please search GitHub for a similar issue or PR before submitting --]
[ ] Documentation issue or request
[/code][/pre]
Description
If I create this API provider definition:
``
delete: tags: --- tasks --- destruction summary: Delete task description: Deletes task by given identifier operationId: 314844b1-3dad-4005-b3b2-d1c9d9463612 parameters: - name: id in: path description: Task identifier to delete required: true type: integer format: int64 responses: '204': description: Task deleted
``
I expect to get NO response, since it's not defined. But I get the result of SQL invocation which is last step that returns some data in the flow. Which is quite unpleasant and unpredictable. It would be better to return either nothing or have an explicit option of returning None in the definition, which would then cause the API provider finishing step not to return anything.