Skip to content
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

Update Multiple Variations Feature with "Beta" Label #302

Open
4 of 5 tasks
vikrampm1 opened this issue Mar 11, 2025 · 3 comments · May be fixed by #311
Open
4 of 5 tasks

Update Multiple Variations Feature with "Beta" Label #302

vikrampm1 opened this issue Mar 11, 2025 · 3 comments · May be fixed by #311
Assignees
Labels
priority: high The issue/PR is high priority—if affect lots of customers substantially, but not critically. status: blocked The issue is blocked from progressing, waiting for another piece of work to be done.
Milestone

Comments

@vikrampm1
Copy link
Contributor

vikrampm1 commented Mar 11, 2025

In addition to the work completed in #235, we need to update the feature to be marked as a "beta" feature. It will be disabled by default, with the ability to enable it via a new extension setting. We will also need to include an admin notice to refer merchants to the feature and the new setting. This update will be shipped as part of v4.9.0, with plans to remove the setting and make the feature default for all merchants in v5.0.0, after gathering feedback from the v4.9.0 release.

  • Create a new extension setting to allow merchants to enable the feature.
  • Add the "beta" label next to the feature setting.
  • Ensure the feature is disabled by default for all merchants.
  • Implement an admin notice in the admin dashboard to inform merchants about the new feature.
  • Update the documentation to reflect the new "beta" status of the feature in v4.9.0 and any instructions on enabling the feature via the new extension setting (maybe included in the document here)
@vikrampm1 vikrampm1 added the priority: high The issue/PR is high priority—if affect lots of customers substantially, but not critically. label Mar 11, 2025
@vikrampm1 vikrampm1 added this to the 4.9.0 milestone Mar 11, 2025
@jeffpaul
Copy link
Contributor

Note that the admin notice should make it clear that it's a beta setting that can be enabled now, that feedback is welcomed, and that the plan is to make it the default behavior in the next major release (but with better, more concise copy than that ;)

@faisal-alvi faisal-alvi linked a pull request Mar 17, 2025 that will close this issue
4 tasks
@vikrampm1 vikrampm1 linked a pull request Mar 17, 2025 that will close this issue
4 tasks
@haszari
Copy link
Member

haszari commented Mar 19, 2025

Note that the admin notice should make it clear that it's a beta setting that can be enabled now, that feedback is welcomed, and that the plan is to make it the default behavior in the next major release (but with better, more concise copy than that ;)

@jeffpaul @dkotter confirming, is a beta notice and opt-in still needed, or is this issue moot now we've decided to go straight to full release?

@vikrampm1
Copy link
Contributor Author

@haszari we won’t be needing this. Just awaiting confirmation from Square before we can close this out and go for the full release.

@jeffpaul jeffpaul added the status: blocked The issue is blocked from progressing, waiting for another piece of work to be done. label Mar 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high The issue/PR is high priority—if affect lots of customers substantially, but not critically. status: blocked The issue is blocked from progressing, waiting for another piece of work to be done.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants