I'm rewriting the generator to something more solid.
In order to simplify creation of other Feliz bindings, I plan on publishing a NuGet with the generator domain model (containing information about components and props) and writer (essentially converts the API model to strings for a component file and props file).
Binding authors can then just instantiate the domain model (either manually or by parsing docs or TS types however they want) and use the model data to generate standard Feliz bindings, which will automatically fix stuff such as erasing types with only inline members etc.
This also makes it easier to change Feliz implementations, e.g. for the new inheritance syntax suggested in #20.
I'm rewriting the generator to something more solid.
In order to simplify creation of other Feliz bindings, I plan on publishing a NuGet with the generator domain model (containing information about components and props) and writer (essentially converts the API model to strings for a component file and props file).
Binding authors can then just instantiate the domain model (either manually or by parsing docs or TS types however they want) and use the model data to generate standard Feliz bindings, which will automatically fix stuff such as erasing types with only inline members etc.
This also makes it easier to change Feliz implementations, e.g. for the new inheritance syntax suggested in #20.