-
Notifications
You must be signed in to change notification settings - Fork 18
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
Have option to use type instead of interfaces for component props #41
Comments
Fair enough! I'll try to get it done for v1.3.0. Thanks for reaching out! |
Sadly, since this feature requires its own flag (which, in turn, requires updating the schema on SchemaStore) as well as other tasks, releasing this in v1.3.0 would delay the release by at least a few days. So it won't be included in v1.3.0, though I'll try to get a special version with this feature as soon as I can after the v1.3 release. Sorry! |
Ok, it's implemented in version The new flag is It's technically an unstable version, but the tests I set up for the feature pass and it seems to behave smoothly. Either way, if you come across any bugs or have any other feedback, please reply here! |
Great work. I'll but it to the test during the next week |
Seems to work as expected. Great work. Keep it up 🚀 |
Thanks! Thanks again for suggesting this. |
I personally prefere to use
type
instead ofinterface
when describing the props in typescript. I see agrippa defaults to usinginterface
It would be nice to have some sort of flag to decide which alternative to use.
The text was updated successfully, but these errors were encountered: