🎩 What? Why?

When the user is unauthorized to do something (e.g. create a new meeting) and there is a direct link to the new meeting page, the user will be redirected to the root of the application.

More sensible would be to ask the user to authenticate themselves.

Testing

• Create an instance with a meetings component and meetings creation enabled for participants
• Write the new meeting path (.../meetings/new) directly to the browser
• See where the user is redirected to

📋 Checklist

• ❓ CONSIDER adding a unit test if your PR resolves an issue.
• ✔️ DO check open PR's to avoid duplicates.
• ✔️ DO keep pull requests small so they can be easily reviewed.
• ✔️ DO build locally before pushing.
• ✔️ DO make sure tests pass.
• ✔️ DO make sure any new changes are documented in docs/.
• ✔️ DO add and modify seeds if necessary.
• ✔️ DO add CHANGELOG upgrade notes if required.
• ✔️ DO add to GraphQL API if there are new public fields.
• ✔️ DO add link to MetaDecidim if it's a new feature.
• ❌AVOID breaking the continuous integration build.
• ❌AVOID making significant changes to the overall architecture.