Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add validation for activation code and error logging for createFamily in Parent Signup flow #1014

Merged
merged 12 commits into from
Feb 3, 2025

Conversation

lucasxsong
Copy link
Collaborator

@lucasxsong lucasxsong commented Jan 17, 2025

Proposed changes

Types of changes

What types of changes does this pull request introduce?

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactoring (non-breaking change that does not add functionality but makes code cleaner or more efficient)
  • Documentation Update
  • Tests (new or updated tests)
  • Style (changes to code styling)
  • CI (continuous integration changes)
  • Repository Maintenance
  • Other (please describe below)

Checklist

  • I have read the guidelines for contributing.
  • The changes in this PR are as small as they can be. They represent one and only one fix or enhancement.
  • Linting checks pass with my changes.
  • Any existing unit tests pass with my changes.
  • Any existing end-to-end tests pass with my changes.
  • I have added tests that prove my fix is effective or that my feature works.
  • If this PR fixes an existing issue, I have added a unit or end-to-end test that will detect if this issue reoccurs.
  • I have added JSDoc comments as appropriate.
  • I have added the necessary documentation to the roar-docs repository.
  • I have shared this PR on the roar-pr-reviews channel (if I have access)
  • I have linked relevant issues (if any)

Justification of missing checklist items

Further comments

@lucasxsong lucasxsong requested a review from a team as a code owner January 17, 2025 18:34
Copy link

github-actions bot commented Jan 17, 2025

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines Unknown% 0 / 0
🔵 Statements Unknown% 0 / 0
🔵 Functions Unknown% 0 / 0
🔵 Branches Unknown% 0 / 0
File CoverageNo changed files found.
Generated in workflow #1283 for commit 4388960 by the Vitest Coverage Report Action

Copy link

github-actions bot commented Jan 17, 2025

Visit the preview URL for this PR (updated for commit 4388960):

https://roar-staging--pr1014-enh-parent-signup-te-7p1petwj.web.app

(expires Fri, 07 Feb 2025 19:15:24 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 2631e9c58fd0104ecbfddd72a62245ddac467460

Copy link

cypress bot commented Jan 17, 2025

roar-dashboard-e2e    Run #10650

Run Properties:  status check passed Passed #10650  •  git commit 4388960f15: E2E Tests for PR 1014 "Add validation for activation code and error logging for ...
Project roar-dashboard-e2e
Branch Review enh/parent-signup-text
Run status status check passed Passed #10650
Run duration 05m 45s
Commit git commit 4388960f15: E2E Tests for PR 1014 "Add validation for activation code and error logging for ...
Committer Adam Richie-Halford
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 0
Tests that did not run due to a developer annotating a test with .skip  Pending 0
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 14
View all changes introduced in this branch ↗︎

src/pages/RegisterFamilyUsers.vue Outdated Show resolved Hide resolved
@lucasxsong lucasxsong changed the title edit text to include roar research portal Add validation for activation code and error logging for createFamily in Parent Signup flow Jan 27, 2025
Emily-ejag
Emily-ejag previously approved these changes Jan 27, 2025
showErrorDialog();
submitted.value = false;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just want to double check that this line was intentionally removed, and not by mistake.

Is this because we want to trigger the conditional rendering of the error messages based on submitted being true after we attempt to submit the form?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is correct, previously the submitted.value = false would prevent the error message from rendering.

.github/workflows/ci.yml Outdated Show resolved Hide resolved
@lucasxsong lucasxsong merged commit 797fe4a into main Feb 3, 2025
22 of 24 checks passed
@lucasxsong lucasxsong deleted the enh/parent-signup-text branch February 3, 2025 17:38
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.

4 participants