Convex components feedback
While components are a great addition to the convex ecosystem, depending on the dev at convex to get the api we might want to build (for the worse or the better) is really limited. Example with the polar component where I want much more control and extend it, I just ending up building it myself because the component is not behaving the way I want. In this particular example, using the checkout component creates a customer without the user intending to subscribe. Instead of fighting with the component implementation which I did for a while, I am now implementing the way I want it to work. And the component is a great help to understand how the polar api works. I just wish there would be a way to implement a plugin element into the convex component logic which would enable to build on top of what convex dev build to save time on the custom implementation I want without bugging the team about it. Curious if it is something in the work? customising schemas and event handling, adding custom functions interacting with the inner tables of the component. If you see what I mean.
2 Replies
The Convex team has said on a few occasions that they plan on releasing something formal that will guide users who want to create their own components, but it's just not a very high priority compared to other things that are more pressing. For now, they say that users can fork any existing component and modify that for their own needs.
Keep an eye on this FAQ entry, which will be updated when we know more about the make-your-own-components guide: https://discord.com/channels/1019350475847499849/1410975297985056850
If you have questions/feedback for specific components, the team prefers to have those discussions in the #components channel.
I'll add two points here:
1. The Polar component needs some love, it's on my list.
2. Extensibility isn't something that needs to be "supported" per se - any individual component can expose api's to do pretty much anything. It's just down to how each specific component is built. But again, I really think the need here is less shipping an extensible core that users can customize and more that the Polar component needs to just work better.
If you open an issue on the Polar component repo with what your experience was and what you needed but didn't have, that would be a huge help: https://github.com/get-convex/polar/issues