Tronje Krop

While this is a kind of misleading error message, it is also clearly stating where and what the error is. I suggest to close it, since adding a mindful wrapper...

@vadeg you can take any `3.0.x` API you know off and mark it as `3.1.0`.

Updating swagger parser to latest version is also not simple. The maximum we can currently achieve without fixing logic is `2.0.18` as I have tested out. Beyond this version we...

True, this is a bug in our release process that releases new CLI versions, while nothing has changed. Semantically v1.1 is correct but consistency requires that we would change the...

@WilliamTwill Thanks for your great contribution, and sorry for the bad support in the last month. I like your request and think we should merge it. However, before I would...

It may also make sense to realign on how to emphasize keywords like `MUST`, `SHOULD`, `RECOMMENDED`, etc. In text we currently use **must**, **should**, ... - also often forgetting the...

I checked this before and back than I found no serious consequences based on this warning for the created `pdf`-file, so I decided to ignore it.

Hi @whiskeysierra @meshcalero, I'm working on my concept to guide by distinguishing on resources. Please give feedback. The main idea is as follows: **Data resources** are resources or properties of...

After talking with @tfrauenstein we extended the perspective to other use cases and resource types ([see Improve Guidance on GET / PUT / PATCH / POST - Draft](https://docs.google.com/presentation/d/1_-geeWAhxJz8QgHEnIgSpakf83aJHPHJoq2YWAC_wy0)).

@dehora @tfrauenstein I did this intentional in public. The slides have no links, and I did not see a reason to keep this work in progress internal. It explains the...