-
Notifications
You must be signed in to change notification settings - Fork 232
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
Link "Complete multiple tasks" research to task list component #3321
Link "Complete multiple tasks" research to task list component #3321
Conversation
✅ You can preview this change here:Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
@stevenjmesser opps - only just spotted that I somehow lost the research section changes when updating the pattern guidance... 🤦 |
The "Research on this pattern" needs to be updated following the design changes.
2de2a51
to
963d914
Compare
Co-authored-by: Colin Rotherham <work@colinr.com>
Co-authored-by: Colin Rotherham <work@colinr.com>
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.
Thanks @frankieroberto
Looks good to me so I'm going to approve this, but we'll get another reviewer to double check the old content to make sure we're not losing anything important
(Like the "Services using this pattern" content)
@colinrotherham thanks! I wasn’t sure if that list was still needed as the pattern is in such widespread use nowadays. Happy to keep it if it is though! |
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.
Looks good to me 👍🏻
…mponent Link "Complete multiple tasks" research to task list component
…mponent Link "Complete multiple tasks" research to task list component
Looks like we forgot to update the research section on the new task list pattern page (as we added the research to the new component page instead).
This updates the content.