Ricky Vetter

Yeah. I feel ya. Probably - but it's lower priority than getting the React part of this repo into better shape (which has obviously been pretty low priority for me...

Hmm. this is interesting. Definitely an interaction issue between the [compiler mangling rules](https://rescript-lang.org/docs/manual/v8.0.0/use-illegal-identifier-names#special-name-mangling-rules-for-js-object-attribute-names) and the PPX. I think the PPX can force it to be avoided if we account for...

Yup! Here's a (very rough) draft of changes I've chatted about. Needs some cleanup before it's ready for prime time. https://gist.github.com/rickyvetter/f0076949c610bdfef61c21da686a608e

Not urgent - we have some code that uses this to create a heterogeneous list but can keep that in .ml for now.

Hey @earksiinni - your research seems to be pretty solid - congrats on digging through this. A lot of the reason this is under-documented is because PPXs are very hard...

Commented in #editorsupport on discord but copying here for better searchibility: Quite tough to correctly recover in this case. I’ve tried a few different things and nothing works very well....

One thought for how we could do this is to use (unfortunately for React stuff we may have to fork) [tyxml](https://github.com/ocsigen/tyxml/blob/master/lib/html_types.mli) to be able to generate this code.

Yes I agree this is a mess. Will be working to make this more consistent. Here is my current plan. Let me know if any pieces of this don't make...

Can you give an example of how context was giving you trouble? It can work fine if you drop out of JSX with something like ``` let context = React.createContext(defaultContextValue);...

@vog did something point you to those other urls? If so we should fix those broken links.