github-actions[bot]
commented
1 month ago Thank you for the pull request!
The activist team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)
If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Development rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!
Maintainer checklist
-
[x] The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution
- The contributor's name and icon in remote commits should be the same as what appears in the PR
- If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for
git config user.emailin their local activist repo
-
[x] The TypeScript and formatting workflows within the PR checks do not indicate new errors in the files changed
-
[x] The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)
-
[x] The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)
netlify[bot]
andrewtavis
Contributor checklist
Description
The event create flow is currently incomplete, with the other create flows being further along. This aims to introduce an event create flow design based on the Figma prototype and existing create flows (e.g. for organizations). The basic features including the paged single form design using
v-ifseem to work. Using arefwith vue models (taken from organizations create flow) enables saving of form data "across" pages, so entries will be populated after moving forwards or backwards. This also makes it easier to send the request data at the end. There are still features and components that will need to be implemented like validation, tooltips, organizer selection, roles, public/private publishing, and invitations.Also, I think I included the QR code changes in this branch. Sorry about that.
Related issue
560