forked from OpenNeo/impress
Matchu
2fb84b0b0f
Hmm, right, okay, we *generally* should have all users imported to Auth0, but this can fail if the cron job is behind or Auth0 rejected the data (e.g. user data in a format it doesn't support). Previously, this would apply the name change in the database, but return Auth0's "The user does not exist." error to the GraphQL client, making it look like the update fully failed. In this change, we handle that case differently: when the Auth0 update fails with a 404, we proceed but log a warning; and when Auth0 fails with an unexpected error, we roll back the database change in addition to raising the error to the client, to keep the behavior obvious and consistent. |
||
|---|---|---|
| .. | ||
| AppearanceLayer.js | ||
| ClosetList.js | ||
| Item.js | ||
| MutationsForSupport.js | ||
| Outfit.js | ||
| Pet.js | ||
| PetAppearance.js | ||
| User.js | ||
| Zone.js | ||