Maksim Danilchenko

@Sanchoyzer thanks for the PR! Could you please make this checking to be optional?

Hi! Yes, it would be cool to include a list of difference between marshmallow < 3 and marshmallow >= 3 into documentation (and I know that many people still use...

@elsimqoz did you add validation middlware to your app?

Oh, @elsimqoz, sorry, I missed that you wrote about response validation. Yes, aiohttp-apispec cannot validate responses. And I don’t think it is necessary. If you don’t think so you are...

Hi! Thank you for your PR! There already exists an issue #46 about it. As you mentioned, it is not only version changing, but there are some differences in Openapi...

@agronholm, I'm agree. We can do this in next major release. But I want to leave it possible to choose between v2 and v3.

> > But I want to leave it possible to choose between v2 and v3. > > I can do that, but are you on board with making v3 the...

Hi! In my opinion the best way is to use FullSchema which includes all fields from NormalSchema and validate needed fields with your custom validation function (and in this function...

Hi! Yes, that's a good idea! But it should be a new function in api (like `create_validation_middleware`). I already add `error_callback` parameter to `setup_aiohttp_apispec` so you can make your [custom...

Hi! There are no ready to use feature for this. But you can extend your schema validation (read here https://marshmallow.readthedocs.io/en/latest/extending.html) with post/preprocessing and checking for invalid keys.