Skip to content

feat: verbose fail messages on invalid invitation

Description

  • the fail messages should now informatively and extensively cover the failure scenarios
  • the redirect from the invitation is now presented after form completion
  • sends also the group in the canInvitationBeAccepted check
  • do not display needs to be verified tooltip if the email in the group application form is the same as the one from the invitation

How to test

  • Pretty much same as !281 (merged). Set up an invitation and change it in DB to EXPIRED, REVOKED and ACCEPTED states. Each time you open the application with the invitation token you should be correctly informed about the wrong state of the invitation.
  • Try different group than the one from invitation in the url.
  • Try to use the email from the invitation in the form and see if needs to be verified tooltip disappears.
  • Check that redirect after completion works as it should, when present in the invitaition.

Author's checklist

  • I have followed the contribution guidelines
  • This MR has been tested or does not change functionality
  • I have added relevant merge request dependencies (if this MR has any)
  • I have added the correct labels
  • I have assigned reviewers (if any are relevant)
  • I have edited the documentation (if the changes require it) or I have noted the need for the change if I do not have access to the documentation
  • I have marked all introduced BREAKING CHANGES or necessary DEPLOYMENT NOTES in the commit message(s)

Reviewer's checklist

  • This MR has been tested or does not change functionality
  • This MR has correct commit message format

Other information

Related issues

Closes STR-1332

Edited by Rastislav Kruták

Merge request reports