-
-
Notifications
You must be signed in to change notification settings - Fork 3
Fix types of automatic and classic runtimes #11
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
Fix types of automatic and classic runtimes #11
Conversation
Nesting properties in a `@typedef` type annotation will generate a namespace, which can be used to generate the required JSX namespace.
This specifies the children prop must be a valid xast child for the automatic runtime, but a valid attribute for the classic runtime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @remcohaszing!
Looks good, seems that in the process it also fixed an ESLint warning, and the linter now wants the disable removed
/home/runner/work/xastscript/xastscript/test-d/classic.tsx: line 10, col 19, Error - '@typescript-eslint/no-unsafe-argument' rule is disabled but never reported. (eslint-comments/no-unused-disable)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One or two small things!
Co-authored-by: Titus <tituswormer@gmail.com>
Initial checklist
Description of changes
This specifies the children prop must be a valid xast child for the automatic runtime, but a valid attribute for the classic runtime.