Check why any object can be put in swagger doc and the swagger tests still pass

[kubantjan]

I just tried to change object in some endpoint and the tests are still passing. Maybe we have something wrong with the test setup (in my case I changed the ouput file in export endpoint)

[kubantjan]

chekc if it is undestandable, and either close or ask.
this is not from txm repo, but from swagger tester (remove the issue from this repo and create it in the other one) and add it to this project.

[kristinagalik]

@kubantjan ked zmenim odpoved endpointu napr export txm event na {} even tho ma response nejake required fields, tak mi hadzu testy response code 200 - lebo sa nedeje uz davnejsie spominany response marshalling. ale ked to testujem cez swagger tak mi to krici ze je nieco zle.. mozno pripadne ak sa ti to este deje vies mi napisat presne kroky ako ten problem zreplikovat prosim?

co som ale nasla je, ze endpoint vo file txm_event_api.py na riadku ~96 (@txm_event_api.route('/<int:txm_event_id>', methods=['PUT'])) sa netestuje - a tipujem ze je to tym ze su 2 PUT requesty co maju velmi podobnu (s tym endpointom hned nad nim /default) url tym padom sa asi nejak "prepise"? ked som tam pridala dake veci do url zrazu ho testovalo

vyzera to ze ked su viacere endpointy s rovnakym typom (napr PUT) ze toto je brane ako rovnake (aj ked z postmana to vola spravne):
route('/slovo', methods=['PUT']) je prepisane ak je nieco ako route('/ineslovo', methods=['PUT'])
ale akonahle ten pattern vyzera inak - napr route('/ineslovo/niecodalsie', methods=['PUT']) tak to zrazu testuje

mam to vyriesit vramci druhej swagger issue mild-blue/txmatching#1040? (je to zmena jedneho riadku)

[kubantjan]

1. @kubantjan will try to reproduce
2. @kristinagalik will create an issue in swagger tester for the same path issue.

[kristinagalik]

@kubantjan tato issue uz je v swagger repe

[kubantjan]

low priority