asc11cat

@kamilmysliwiec any thoughts on PR? #2088 was closed due to fastify-multer being a too young library, but a year has passed since then

The 'definitions' keyword in the component(3.0)/definition(2.0) item schema itself is not allowed at all, it is allowed only in top-lvl as 'definition' if we are using the OpenAPI 2.0 version....

> > @mikaelkaron would you like to work on it? > > I’d love to help out, but not really in a place where I think I can dig into...

This issue is specific for 0.6 ML and seems to be fixed in https://github.com/Baydock/UnityExplorer-NewML fork @jadis0x @vvdashdash @Kalybr50

@mikaelkaron as for now I'm taking the first approach, and I see a few caveats here: If we have both 'properties' and 'definitions' in json-schema - we need to merge...

Finished the fixes for openapi, seems to work fine. Definitions are now being merged with properties at transformDefsToComponents helper, solutions is kind of hacky, but I don't really see any...

@ivan-tymoshenko I faced some issues related to relative definitions, and will appreciate if you can take a look Right now when we will try to do something like this(even on...

> > so we should patch the relative definitions to absolute? > > According to json schema spec if you define subschema with a $id property the root inside this...

@ivan-tymoshenko finally got some time to finish this PR Now local references are being transformed to absolute, and 'definitions' keyword is being merged with 'properties', with precedence to the last...

> I will check it deeply ASAP. But I have a question for now. I think that problem is in the [json-schema-resolver](https://github.com/Eomm/json-schema-resolver). Shouldn't functions like `localSchemaRefToAbs` and `patchDefinitionsKeywordInSchema` be there?...