woonki

Is it what you want at the beginning? (backward compatibility) 😄 Switching the V4 as default is an effortless task like a finger snap. One thing came to mind is...

I think there is a setting for "do nothing", not adding `"reason": { ... }` nor `"jsx": { ... }`. If user doesn't add any of them, jsx ppx will...

How about throwing more informative error message, in case user didn't add the jsx configuration, but has written JSX expressions or attribute `@react.componet`?

Before further discussion, let me clear your intention. 1. no configuration at all -> V4 + classic 2. configuration -> works as configuration Is it correct?

I got your point. Let me write down some user stories to make it clear. First, `"reason": 3` + V3 users -> JSX V4 + classic as default If user...

Yes, I think making V4 + classic as default brings the new feature with impact.

Oh, we can still make not triggering the jsx ppx if user doesn't have any configuration about jsx at all.

If we make V4 + classic as default, then submodules in dependencies will be affected by the same default, right? Is it your intention?

It is very clever idea! If we update some react component such as Context, Fragment with `@react.component` then everything will work accordingly! Same to other submodules. Anyway, some components in...

Beside the decision about V4 as default, there is no stuffs left in progress. Can you guide me how to fill the detailed documentation?