Repository navigation
Replies: 1 comment
|
I've finally decided against this. It's much easier to make those decisions user-land, as outlined in the code samples, which also leaves this lib pure. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Instead of having them as options, I think it would be better to ship composing hooks, basically as they are outlined in the readme already:
This would allow me to keep the base interface minimalistic, while at the same time offer solutions to a seemingly frequent use case.
This is how it would look I think:
The only downside that I would probably have to provide polyfilled builds as well, so maybe:
And of course I would have to run the whole test suite and more on these builds.
I'll just leave this issue here to assess demand.
All reactions