feat: switch model renders

[jonaslagoni]

Description
This PR switches from QuickType model generation to our own implementation.

• It removes the need for wrapping schemas inside messages and instead uses schemas directly.
• Switches to a new hook.

Related issue(s)
Solves asyncapi/shape-up-process#50

[magicmatatjahu]

Very good! Only two comments :)

[fmvilas]

I'm curious why you're generating the models on a hook instead of using these functions in a $$schema$$.js file. IMHO, it would be simpler to read.

[magicmatatjahu]

@fmvilas

I'm curious why you're generating the models on a hook instead of using these functions in a $$schema$$.js file. IMHO, it would be simpler to read.

asyncapi/generator#515 😅

[fmvilas]

🤦 Thanks for pointing me to this, Maciej!

[jonaslagoni]

I'm curious why you're generating the models on a hook instead of using these functions in a $$schema$$.js file. IMHO, it would be simpler to read.

@fmvilas I have no preferences, this is just how I did it with QuickType and to not mix different changes into one PR I will keep it like this. But it is a good point.

I am however unsure how I can even achieve this without the following issue to be addressed first: asyncapi/generator-react-sdk#10

Then I would have to iterate messages myself and generate models per payload 🤔

[jonaslagoni]

Why? I think you get the schema variable in the rendering context. It would be just a matter of calling the library with schema.json(). Or am I missing something?

Short answer yes you could do that. The problem is there are multiple ways of doing it depending on your use-case. If you used $$message$$ you could wrap all schemas for a specific message into a wrapper class, if you used $$objectSchema$$ (without this issue) you would probably generate multiple schemas depending on how you references them in your document with some duplicates that are never used.

However without this issue I don't think I would be able to incorporate it into a file schema the way I want it to😄

[fmvilas]

I don't completely follow but don't want to make you lose time. Let's discuss this next Wednesday on the retrospective 👍

[jonaslagoni]

@fmvilas created an issue to further investigate - #54

[fmvilas]

LGTM 👍

[magicmatatjahu]

LGTM! You probably wait for asyncapi/generator-react-sdk#10, is it true?

[jonaslagoni]

@magicmatatjahu no I will solve the conflicts in a sec. #54 will be for waiting for that issue you linked :)

[asyncapi-bot]

🎉 This PR is included in version 0.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[jonaslagoni]

@all-contributors please add @fmvilas review

[allcontributors]

@jonaslagoni

I've put up a pull request to add @fmvilas! 🎉