Support for using a JSON string rather than a URL path?

[jszwedko]

I have a scenario where I need to preprocess the swagger.json before giving it to apivore to validate (translating x-nullable to adding "null" to the type list for a given property). I can take a crack at implementing this, but wanted to see if it the change would be accepted first.

Thank you!

[hornc]

Hi @jszwedko, thanks for getting in touch! I've had a look at your use case from the sfhomeless-api. We have run into problems with types and nulls with other tools also. If I understand you correctly, what you are proposing is a more general feature though, accepting any raw json, rather than getting apivore to recognise x-nullable?

The general feature would be useful, and definitely accepted. The main thing we ask is that there are adequate tests provided for any new feature (see our contributing guidelines )

I might need to look into how others are using x-nullable to get a feel if apivore should know about it or not. It might be a bit fragile? I get the impression the hope is that the other tools will catch up to support multi-types / type + null soon?

I'm happy to discuss further and review code etc -- I'm glad you are finding apivore useful in your project!

Cheers!

[jszwedko]

Hey! Apologies for the delay. Yeah I was thinking, rather than adding support for x-nullable, just adding support for transforming the JSON before passing to apivore would be more flexible and also allow a workaround for this case..

I'm also mixed about supporting x-nullable directly as this does feel like something that swagger will address soon (hopefully!).

I'll put together a PR for using a string rather than a route. I definitely appreciate the increased confidence apivore gives me that my API is complying with the spec.

[ashoda]

Hi @jszwedko, closing this issue in favor of #100