Proposal: design changes in web framework integration

[sumitparakh]

While working on Vue3 integration, I realized that it might not be a good idea to write altogether a separate implementation for vue3.

If we integrate vue3 then we might have to show 2 Vue icons in the web frameworks list in landing page. One for vue3 and another one for vue (legacy version).

What if vue releases another major version in future which involves breaking changes like vue3. Are we going to write a new code-gen implementation and add a new framework list in the landing page again? It might increase our maintenance cost.

I propose that we change our web framework integration strategy a bit and also take versions(1.x,2.x, 3.x etc.) and language (JS or TS or Dart - AngularDart for eg. ) in the scope. Both would be optional of-course.

1. Any web framework can have multiple versions with or without breaking changes
2. Any web framework can be in multiple languages - Javascript or Typescript or Dart

After we implement the design changes, we should be able to integrate different versions and/or languages of any web framework under one umbrella.

Let's take vue as an example. New versions with breaking changes might keep getting added. How are we going to keep maintaining those integrations?

@manekinekko @Jefiozie

[manekinekko]

Thank you @sumitparakh for bringing this up. This was something we were considering but we were lacking time to work on it.

Would you want to give this a try?

[sumitparakh]

Yes @manekinekko. I want to give it a try.