-
Notifications
You must be signed in to change notification settings - Fork 70
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
Resolve content model tentacles on 10089 Events checkbox #15641
Comments
Estimate doesn't factor Lovell complexity. Daniel to talk to AP folks and update as needed with Lovell in mind. |
Mid-sprint Update 10/19/23When taking on this ticket, we were planning no architectural changes on the backend, and instead making the frontend (content-build) robust enough to handle both a single value and an array of values. However, this approach had a lot of technical debt built in, and little risk mitigation was possible. Because of this, we are pivoting to a different architecture: Backend Changes
Frontend (content-build) Changes
Overall this approach is much safer, since we aren't touching the structure of an existing field, but adding another field which is brand new to the ecosystem. |
@dsasser I like this and also: it smells like we may get questions at code review time. Would it be worth bouncing this off any other Drupal folks for smell testing before we fully commit? Or feels very safe / uncontroversial as a fix? |
Getting feedback during review time is adequate in this case. |
Testing notes: Tugboat with feature toggle enabled: https://cms-ytipldihujdcko41uemzx3w18e31hyof.ci.cms.va.gov/admin/config/system/feature_toggle
Other FE tests:Listings:
Recurring events: expected behaviorIn production today, for a recurring event, only the next upcoming instance will appear in the Upcoming filter.
https://www.va.gov/outreach-and-events/events/61561/
|
Deployment Plan
Jill meddled hereI moved this list as checkboxes into the body of the ticket, so it's easy to see next to ACs for modern state of truth. |
@laflannery when you get a chance, could you review this PR for a11y + breadcrumb signoff? Tugboat is hit or miss today, but you should be able to get in eventually if you keep trying. There is a list of existing FE pages that Jill created while testing that might be of interest to you. |
@dsasser I got in for a bit but wasn't able to test everything yet. However I do have one general QA item I wanted to mention - I saw this issue that I had flagged as a D10 issue and thought had been resolved in a previous ticket. Is it a problem that it's here in this tugboat? |
@dsasser @laflanner I see what Laura is seeing here: https://cms-ytipldihujdcko41uemzx3w18e31hyof.ci.cms.va.gov/node/62493/edit I tried to repro that, using this new event: https://cms-ytipldihujdcko41uemzx3w18e31hyof.ci.cms.va.gov/node/62522/edit
Then got a 502. 😂 but will check when it's back up, re: whether the 2nd date fields appear. |
I'm still not clear how to reproduce what you and @laflannery are seeing w/ the 2nd set of date fields. Noting that this would be an unexpected change, since we didn't change those fields in any way intentionally. |
@dsasser and @jilladams some notes:
|
The D10 note is interesting - I know the CMS team was most recently planning to ship that 1st week of November. So I just realized: wow, we need to take that into account with this launch. I'll ping CMS channelt o confirm timing. |
@laflannery what is the behavior on staging/prod? |
Yes, good call. If in Staging, officially not tied to this feature and we can/should handle separately. |
So back to what I was actually supposed to be reviewing, using the table from Jill above: Scenario 1
Scenario 2
Scenario 3
Scenario 4
CMS
|
( Noting: all test data at tugboat links i comments above got blown away by Tugboat refresh. ) |
Everything is approved by me, breadcrumbs look good and not a11y issues! |
Description
#10089 added an Events checkbox to the Events form.
This change shipped and broke the content model in the front end in 2 known places:
Slack threads
Topline for DaveC
Engineering notes
Feature Toggle may still be "ON" in prod, despite the revert of our code which created it.
We need to be careful about the
FEATURE_EVENT_OUTREACH_CHECKBOX
feature toggle being deployed as "enabled". The latest CMS mirror is showing it as enabled, but unsure if this was because the snapshot was taken before the revert was deployed.Everywhere field_listing is used in templates/queries
ACs.
FEATURE_EVENT_OUTREACH_CHECKBOX
does not deploy as 'enabled'.Deployment Plan
The text was updated successfully, but these errors were encountered: