@erchwy It's because we don't want to eager-load the organization list when useUser() is called.
This is one of our eternal debates: Do DX benefits justify loading more data than strictly necessary? Loading extra data inherently takes extra time - how much is too much? #buildinpublic
#buildinpublic This afternoon we'll try making @stripe subscription data available to useUser()
Optimistic we can read customer.subscriptions just-in-time for the proof-of-concept, but we'll need to use webhooks in the future: stripe.com/docs/api/custo…
When changelogs showed early signs of success, we started thinking about how else we can #buildinpublic
So far, our second favorite activity has been building and sharing integrations with third parties. Today, this is pretty clear from the "Product" menu on our homepage: