-
Notifications
You must be signed in to change notification settings - Fork 469
Required shim for "PervasivesU", gentype #6807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This might be related. I just tried to do a gentype export on a function that takes a import type {Keyboard_t as ReactEvent_Keyboard_t} from '@rescript/react/src/ReactEvent.gen.tsx'; |
gentype special-cases type |
The type Jsx.element can show user-side in ppx V4 (at least), and affects gentype too. It special-cases `React.element`, and needs to then special-case `Jsx.element` too. Fixes #6807
The case for |
The type Jsx.element can show user-side in ppx V4 (at least), and affects gentype too. It special-cases `React.element`, and needs to then special-case `Jsx.element` too. Fixes #6807
The type Jsx.element can show user-side in ppx V4 (at least), and affects gentype too. It special-cases `React.element`, and needs to then special-case `Jsx.element` too. Fixes #6807
The type Jsx.element can show user-side in ppx V4 (at least), and affects gentype too. It special-cases `React.element`, and needs to then special-case `Jsx.element` too. Fixes #6807 # Conflicts: # CHANGELOG.md
The type Jsx.element can show user-side in ppx V4 (at least), and affects gentype too. It special-cases `React.element`, and needs to then special-case `Jsx.element` too. Fixes #6807 # Conflicts: # CHANGELOG.md
The type Jsx.element can show user-side in ppx V4 (at least), and affects gentype too. It special-cases `React.element`, and needs to then special-case `Jsx.element` too. Fixes #6807 # Conflicts: # CHANGELOG.md
The type Jsx.element can show user-side in ppx V4 (at least), and affects gentype too. It special-cases `React.element`, and needs to then special-case `Jsx.element` too. Fixes #6807 # Conflicts: # CHANGELOG.md
I created a new empty ReScript project with the latest stuff and a small "Hello World" React component seems to work. BUT there is an error in the VS Code reporting. The generated
.gen.tsx
files has this code...The error is...
I had no idea how to fix this. Using...
This separate bug in the compiler has a repro scenario where the developer fixed this problem I ran into by creating a shim.
#6624
https://github.com/WhyThat/gentype-error-reproduction/blob/main/src/shims/PervasivesU.shim.ts
I think that (1) the shim should not be required, or (2) the documentation for getting started with ReScript and React needs to explain how to make the shim. Actually now I see that TypeScript shims have been deprecated so I'm confused how I'm supposed to handle this issue.
My rescript.json file...
The text was updated successfully, but these errors were encountered: