Skip to content
This repository has been archived by the owner on Jan 11, 2024. It is now read-only.

Remove support for user testing - the mainToggle prop #487

Open
christiemolloy opened this issue May 10, 2021 · 2 comments
Open

Remove support for user testing - the mainToggle prop #487

christiemolloy opened this issue May 10, 2021 · 2 comments
Labels
refactor / clean up

Comments

@christiemolloy
Copy link
Contributor

@jgiardino do you think we can remove mainToggle anymore ? or are you still testing / think we'll need it in the future?
@christiemolloy christiemolloy added the question Further information is requested label May 10, 2021
@christiemolloy christiemolloy changed the title Do we need mainToggle anymore? Do we still need to support user testing (e.g. mainToggle) ? May 10, 2021
@jgiardino
Copy link
Contributor

I have no immediate plans to create mock UI for testing. Now that we have fully functioning UI, I'm not sure this is needed. And we can always show alternate UI in mockups if needed.

@christiemolloy
Copy link
Contributor Author

I'd agree with that. I think we can go ahead and remove mainToggle for now. We could always keep the user-testing URL param in the code for the future.

@christiemolloy christiemolloy removed the question Further information is requested label May 12, 2021
@christiemolloy christiemolloy changed the title Do we still need to support user testing (e.g. mainToggle) ? Remove support for user testing - the mainToggle prop May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
refactor / clean up
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@christiemolloy @jgiardino