-
Notifications
You must be signed in to change notification settings - Fork 57
Description
The UserProfileForm has a hard dependency on a route that must be implemented by the developer in their backend server. Right now it is hard-coded to post to the /me endpoint, which creates confusion because the Client API (and current framework integrations) provide this as a read-only endpoint that does not accept a POST. It is up to the developer to implement their own route for modifying the user object, in our other examples we show the developer how to setup a /profile route for this purpose.
I think this component should be removed from the core SDK and moved into an example project, but I'm open to other ideas. At the very least, the endpoint needs to be changed from /me to remove confusion with our read-only endpoint, changing it to /profile would be the most congruent.