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

Correct blinking disabled for nested question-with-follow-up #4988

Merged
merged 2 commits into from
Nov 19, 2024

Conversation

powersurge360
Copy link
Contributor

@powersurge360 powersurge360 commented Nov 15, 2024

Link to pivotal/JIRA issue

Is PM acceptance required? (delete one)

  • Yes - don't merge until JIRA issue is accepted!

Reminder: merge main into this branch and get green tests before merging to main

What was done?

  • This changes the nested follow up normalization code to only work on direct descendants. This stops the issue of nested question with follow up boxes from being picked up
  • 🚨 This feature is not unit tested. It may be that there are places where this will break existing functionality. I went through and checked as much as I could think of but it's something to be vigilant for.

How to test?

  • Navigate through NC flow
  • Transfer any persona
  • Select yes on nc-sales-use-tax page
  • Select second option `I kept a complete
  • Click money field input box

Copy link

Heroku app: https://gyr-review-app-4988-0fc0c3f2ddd0.herokuapp.com/
View logs: heroku logs --app gyr-review-app-4988 (optionally add --tail)

$container.find('.question-with-follow-up__follow-up input, .question-with-follow-up__follow-up select').attr('disabled', true);
$container.find('.question-with-follow-up__follow-up').hide();
$container.find('> .question-with-follow-up__follow-up input, .question-with-follow-up__follow-up select').attr('disabled', true);
$container.find('> .question-with-follow-up__follow-up').hide();
Copy link
Contributor

@arinchoi03 arinchoi03 Nov 15, 2024

Choose a reason for hiding this comment

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

just a note that this used to exist in the previous followup implementation but it was removed in this PR codeforamerica/honeycrisp-gem#312 for honeycrisp gem -- we might not have any instances of followup questions after none of the above checkboxes

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm not sure I see the direct descendent selector in that diff?

Copy link
Contributor

Choose a reason for hiding this comment

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

Oops wrong one -- I'll post the right one after lunch

Copy link
Contributor

@arinchoi03 arinchoi03 Nov 15, 2024

Choose a reason for hiding this comment

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

4f6da69

I was mistaken- it seemed like we solved for this case a long time ago and it was a tax-specific code addition to honeycrisp.js that was never implemented in the gem, so when I copied over the recent version we lost the existing fix -- which makes me feel a lot better about this as this is more like a return to status quo

@powersurge360
Copy link
Contributor Author

Mike noted that even though the UX is correct, the form fields in nested attributes may still be active. Users will have to go out of their way to get to that funky functionality but it is possible. A full refactor of the JS for follow up questions (and perhaps even some changes into the structure of the HTML) is likely to solve all sharp edges.

@arinchoi03
Copy link
Contributor

arinchoi03 commented Nov 15, 2024

@powersurge360 can we document how we might get into that funky state & create a ticket/issue?

cc @aloverso on the input blinking issue

@powersurge360 powersurge360 merged commit 9986f6c into main Nov 19, 2024
7 checks passed
@powersurge360 powersurge360 deleted the FYST-1174/correct-nested-question-with-follow-up branch November 19, 2024 16:31
@powersurge360
Copy link
Contributor Author

@powersurge360 can we document how we might get into that funky state & create a ticket/issue?

cc @aloverso on the input blinking issue

https://codeforamerica.atlassian.net/browse/FYST-1211

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.

2 participants