I am considering having @component fields take two parameters, a la:
iso(`
field Foo.Bar @component { id }
`)(function(props, additionalProps) {
});
Pros:
props will be automatically typed, and additionalProps can be provided a type by the user. I don't see a good way to type the remaining props otherwise, without having the user import the generated type Foo__Bar__param
Cons:
It doesn't "look" like a component, so some people will be put off by this. Maybe some tooling will not work, e.g. eslint rules might complain about calling hooks. I don't know.
I am considering having @component fields take two parameters, a la:
Pros:
props
will be automatically typed, andadditionalProps
can be provided a type by the user. I don't see a good way to type the remaining props otherwise, without having the user import the generated typeFoo__Bar__param
Cons: