-
Notifications
You must be signed in to change notification settings - Fork 21
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
Bug fix for disabled button #3408
Conversation
QA Summary
Test CoverageCoverage report for `packages/client`
Coverage report for `packages/server`
|
Terraform Summary
Hint: If "Terraform Format & Style" failed, run OutputValidation Output
Plan Summary
Pusher: @greg-adams, Action: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@greg-adams I like the direction here, but given that our Staging and Production environments have the ID of 0
I'm not sure this change will resolve the problem outside of dev environments with no existing data.
If we wanted to go this route in Staging / Production, I think we would need to migrate existing records in the DB, as well as any FK references to the current IDs.
updated to resolve issue without data changes |
Ticket #3380
Description
Bug fix for unwanted disabled submit button in Team Status section. The template syntax for this boolean is correct, however, the issue is caused by seed data which uses an id of
0
, which is falsy in JS. I'd suggest we should always avoid using number 0 for a record id, and it appears the default in Postgres is to start a sequence with 1.Screenshots / Demo Video
Testing
Manual testing notes:
Automated and Unit Tests
Manual tests for Reviewer
Checklist