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

Gracefully removes mobile ucr version drop down from app advanced settings #35046

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

ajeety4
Copy link
Contributor

@ajeety4 ajeety4 commented Aug 27, 2024

Product Description

NOTE: This PR will not be merged unless all apps are migrated to v2 first. The migration work is planned and will be picked up soon.

This is only UI change where it gracefully removes mobile ucr version drop down from app advanced settings.

This uses an existing way to disable a setting and works as below

  • if the app is on the intended version, then the setting is not shown.
  • f the app is not on the intended version , the setting is shown with a user friendly message to ask user to select the correct version.

Demo:

UI.Remove.mobile.ucr.dropdown.mp4

Technical Summary

Ticket

Feature Flag

Mobile UCR Feature Flag

Safety Assurance

Safety story

Local testing done. Small UI change which is safe and non-breaking.

Automated test coverage

None

QA Plan

None

Rollback instructions

  • This PR can be reverted after deploy with no further considerations

Labels & Review

  • Risk label is set correctly
  • The set of people pinged as reviewers is appropriate for the level of risk of the change

@ajeety4 ajeety4 added product/feature-flag Change will only affect users who have a specific feature flag enabled Open for review: do not merge A work in progress labels Aug 27, 2024
Copy link
Contributor

@zandre-eng zandre-eng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great that we could get this implemented with such minimal code changes!

@@ -156,6 +156,9 @@
values:
- ['2.0', '2.0']
default: '2.0'
disabled: true
disabled_txt: Oops! This setting has been discontinued. We recommend you change this setting to Version 2, and it will no longer appear on your settings page.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this get translated at a later point when it gets shown in the UI? If not then it might be good to consider translating this text.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, just a nitpick on the wording of the text. Perhaps it can be something like the following:
Oops! This setting has been discontinued. We recommend you change this setting to Version 2. Upon doing so this setting will no longer appear on this settings page.

The above might just make it a bit more clear as to when the setting will stop appearing on the page. No strong feelings however, and fine to leave as is if you feel the current text is clear enough.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love the idea that these be translated, but I think that might be a significantly heavier lift. I think it's okay to continue doing what the rest of this file does.

It is also worth noting that since you copied and pasted the exact text from line 111 that Danny wrote in 2014 (!), if that text is already translated, then this text will be translated too

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I did use the exact same text.
Just did a quick check and these messages in the yaml file are indeed translated.

@@ -156,6 +156,9 @@
values:
- ['2.0', '2.0']
default: '2.0'
disabled: true
disabled_txt: Oops! This setting has been discontinued. We recommend you change this setting to Version 2, and it will no longer appear on your settings page.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love the idea that these be translated, but I think that might be a significantly heavier lift. I think it's okay to continue doing what the rest of this file does.

It is also worth noting that since you copied and pasted the exact text from line 111 that Danny wrote in 2014 (!), if that text is already translated, then this text will be translated too

@ajeety4
Copy link
Contributor Author

ajeety4 commented Aug 28, 2024

NOTE: Keeping this PR in draft only to avoid accidental merge since the related v2 migrations could take some amount of time to get done

default: '1.0'
default: '2.0'
disabled: true
disabled_txt: Oops! This setting has been discontinued. We recommend you change this setting to Version 2. Upon doing so this setting will no longer appear on this page.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: do we need "Oops"? Isn't that in case of errors?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. Addressed in bc58280 (merged with earlier commit)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Open for review: do not merge A work in progress product/feature-flag Change will only affect users who have a specific feature flag enabled
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants