Is this still the case, or did `swagger2-2.3` fixed this? cc @fizruk I'm holding the release on this issue.
Is this still the case, or did
swagger2-2.3fixed this? cc @fizrukI'm holding the release on this issue.