Skip to content

Conversation

RomanBf
Copy link

@RomanBf RomanBf commented May 20, 2018

Fixes this issue.
Without checking for this error, when rate-limiting kicks in it throws an error because fieldId is set to "timeToReset" (and this field does not exist). The whole accounts-form then is disabled and unresponsive, without informing the user about what's going on (you can only see the error message in the client-side browser console).

Fixes [this issue](meteor-useraccounts/core#629).
Without checking for this error, when rate-limiting kicks in it throws an error because `fieldId` is set to "timeToReset" (and this field does not exist). The whole accounts-form then is disabled and unresponsive, without informing the user about what's going on (you can only see the error message in the client-side browser console).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant