Rishabh Poddar

Maybe a better interface would be to pass a "LOADING" status to the children component instead? So the context would become: ``` { status: "LOADING" } | { status: "READY",...

Hey @gmwill934 , Sure! Help would be much appreciated. I like the idea of returning a `isLoading` param from `useSessionContext()`. However, this would be a breaking change since right now,...

This is a good idea. However, I think we should postpone this to post the MVP launch. - If someone adds a decorator, will the formField error message still show...

> That's a fair point! That means using decorators implies that you have to disable the default implementation. That was the reason why we moved everything to the init in...

Let's discuss this over a call.

A better idea could be that the provided component is a wrapper to the actual text input and its label. This way, we can control not only what's below the...

@jeremylynch yes. We are working on adding user meta data which will enable this. However, the way we plan on doing this is via a form post sign up instead...

@execreate we have already released the `usermetadata` recipe in the SDKs and the core. The docs are yet to be released for it. Should be done sometime in this week...

Should we make changes to the supertokens-website SDK first before making changes here?

# Feedback (WIP): - [x] We should rename “ACCESS_TOKEN_UPDATED” to “ACCESS_TOKEN_PAYLOAD_UPDATED” - [x] Make role keys in access token smaller -> `st-email-verification` -> `st-ev` - [x] All examples in the...