Closed mdellweg closed 4 years ago
I guess this breaks FAM tests as the fixtures contain uppercase True in queries for "thin"?
Also, how does that influence, if at all, unicode params (on Python 2)? Probably safer to avoid the non-boolean str cast and let requests decide what to do?
Also, how does that influence, if at all, unicode params (on Python 2)? Probably safer to avoid the non-boolean str cast and let requests decide what to do?
As in "not change the part that is not broken"? I'll do that. But the fam fixtures will still be wrong... I sure hope that the other parts of the api accept "true" where we sent "True" before.
My best guess is: it didn't, but also didn't complain. 🤷♀️
https://github.com/theforeman/foreman/blob/d00fc37a68839f8bf823969880339c9343eacd4c/app/controllers/api/v2/hosts_controller.rb#L44 looks like "any string that's not 'false' will be true"?
Yeah...
There is thin=False but the response in the next lines only contains id and name…
I which order are we supposed to fix/merge this?
I think we can just accept the failing test here for now, merge it, release a new version and then re-record/sed the fixtures.
Also having #73 in would be good for the release (and the vendoring ;))
@mdellweg would you mind rebasing this once, so it runs with pylint, just to be sure? :)
Ah, needs rebase anyways whistle
pylint seems happy.