Michał Zubkowicz

@dmythro , good point. I think possibility easy include / exclude / move it's only solution to solve these issues. I don't think you can avoid politics at all here.

Query params as class can be usable, when all get params are inherited from some shared model or for example when defining fields swagger. I've got such case now. Maybe...

Same problem here, Play 2.5.6 and swagger-play2 1.5.2

If you want use swagger with play 2.5.6 you can use our temporary fork git clone https://[email protected]/michal_zubkowicz/swagger-play.git cd swagger-play/play-2.5/swagger-play2 /opt/sbt/bin/sbt ++2.11.7 publish-local and then in build.sbt: "io.swagger" %% "swagger-play2" %...

Hi. I've accidentally revoked access to repository. Please try with this new url. git clone https://[email protected]/michal_zubkowicz/swagger-play.git I've updated original answer also. Sorry for inconvenience ;)

Hmm, it looks like some kind of bitbucket bug, this repository is public for sure. Try to clone by https, it should work then: git clone https://[email protected]/michal_zubkowicz/swagger-play.git

I'm using it in few 2.11.8 projects. What's the problem?

@ganz14, Quick and dirty - add key property `