-
Notifications
You must be signed in to change notification settings - Fork 31
ntp: prep a re-usable switch #1339
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
Conversation
✅ Deploy Preview for content-scope-scripts ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Temporary Branch UpdateThe temporary branch has been updated with the latest changes. Below are the details:
Please use the above install command to update to the latest version. |
[Beta] Generated file diffTime updated: Thu, 19 Dec 2024 10:11:26 GMT Integration
File has changed Windows
File has changed Apple
File has changed |
mgurgel
left a comment
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.
🏆

Asana Task/Github Issue: https://app.asana.com/0/1201141132935289/1209013497841867/f
Description
Using the ‘rule of 3’ -> in the NTP I need a switch component. We already implemented a switch in Onboarding, and then again in DuckPlayer (because the DuckPlayer one was quite different). But now I need exactly the same as in Onboarding, so I’m takingn the time to make it re-usable.
NOTE: We’ve realised that we must not use globals for components we want to share - that’s why the refactored components works how it does. You must be able to configure the components where you use them, since some pages will have a mix of light+dark
Testing Steps
Checklist
Please tick all that apply: