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

Onboarding Highlights Ship Review #3380

Merged

Conversation

alessandroboron
Copy link
Contributor

@alessandroboron alessandroboron commented Sep 23, 2024

Task/Issue URL: https://app.asana.com/0/1206329551987282/1208291253556033/f

Description:

This PR includes changes and fixes that have been addressed during the Ship Review.

Commits are mostly self contained and address each Ship Review comment, so you can review each commit separately if you prefer.
The PR also includes the copy translations.

Steps to test this PR:
Test Scenario 1, 2, and 3 of Ship Review Testing section

Definition of Done (Internal Only):

Copy Testing:

  • Use of correct apostrophes in new copy, ie rather than '

Orientation Testing:

  • Portrait
  • Landscape

Device Testing:

  • iPhone SE (1st Gen)
  • iPhone 8
  • iPhone X
  • iPhone 14 Pro
  • iPad

OS Testing:

  • iOS 15
  • iOS 16
  • iOS 17

Theme Testing:

  • Light theme
  • Dark theme

Internal references:

Software Engineering Expectations
Technical Design Template

Copy link

github-actions bot commented Sep 23, 2024

Warnings
⚠️ PR has more than 500 lines of code changing. Consider splitting into smaller PRs if possible.
Messages
📖

You seem to be updating localized strings. Make sure that you request translations and include translated strings before you ship your change. See Localization Guidelines for more information.

Generated by 🚫 dangerJS against 5435710

Copy link
Contributor

@brindy brindy left a comment

Choose a reason for hiding this comment

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

Added a note to the asana task with the scenarios in them. Couple of comments here too.

block()
})

RunLoop.main.add(timer, forMode: .common)
Copy link
Contributor

Choose a reason for hiding this comment

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

Nothing about this class suggests this is for the main loop. Can that be more explicit? Given you've put it in a common location I'd be tempted to also pass in the RunLoop to use, maybe default it to .current which is what I would expect as a dev tbh.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fair point, I will update this and give the dev ability to choose which RunLoop to use.

Copy link
Contributor Author

@alessandroboron alessandroboron Sep 24, 2024

Choose a reason for hiding this comment

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

updated, I’ve also added the RunLoop.Mode as parameter

import Foundation

/// A class that provides a debouncing mechanism.
public final class Debouncer {
Copy link
Contributor

Choose a reason for hiding this comment

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

Seems old school to implement this with timers when Combine has one built in but:

1/ Then you'd need to pass in the debounce time in the constructor
2/ It's probably just as many lines of code as this

No change required.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I’m fine to change to use Combine under the hood if we want, but yeah probably the lines of code will be very similar.

@@ -144,7 +144,7 @@ struct ProgressBarGradient: View {
let nextStep = stepInfo.currentStep < stepInfo.totalSteps ? stepInfo.currentStep + 1 : 1
stepInfo = OnboardingProgressIndicator.StepInfo(currentStep: nextStep, totalSteps: stepInfo.totalSteps)
}, label: {
Text("Update Progress")
Text(verbatim: "Update Progress")
Copy link
Contributor

Choose a reason for hiding this comment

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

Why did this change? verbatim means everyone will see "Update Progress" but shouldn't it be localised?

Copy link
Contributor Author

@alessandroboron alessandroboron Sep 24, 2024

Choose a reason for hiding this comment

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

Ah this is just a SwiftUI preview I built to test the behaviour of the progress bar. When I tap that button I simulate the progress bar increasing its progress. At translation time I noticed it was translating that string.

@alessandroboron alessandroboron force-pushed the alessandro/onboarding-highlights-ship-review branch from 3020e0d to 4445e45 Compare September 24, 2024 06:46
@alessandroboron
Copy link
Contributor Author

Added a note to the asana task with the scenarios in them. Couple of comments here too.

I addressed the PR feedback and replied to your Asana comments. I also fixed other bugs I found during testing. All explained in Asana task

Copy link
Contributor

@brindy brindy left a comment

Choose a reason for hiding this comment

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

Seems to work fine now, except for the bay thing. Am approving but maybe we'll change eBay?

Copy link
Contributor

@brindy brindy left a comment

Choose a reason for hiding this comment

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

LGTM - tested each variant starts the expected flow

Copy link
Contributor

@brindy brindy left a comment

Choose a reason for hiding this comment

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

LGTM - tested each variant starts the expected flow

@alessandroboron alessandroboron changed the base branch from main to release/7.139.0 September 26, 2024 10:08
alessandroboron and others added 20 commits September 26, 2024 20:10
…uent dialog should be presented, reloading the page would show again the dialog
…rowsing data and navigate to the same website before tapping on end of journey CTA
…sing data twice before tapping on the end of journey CTA
… website when opening a new tab and visit again the website
…ked trackers dialog on anonymous searches page
@alessandroboron alessandroboron force-pushed the alessandro/onboarding-highlights-ship-review branch from 9bacb29 to 19e2495 Compare September 26, 2024 10:10
@alessandroboron alessandroboron merged commit 3184192 into release/7.139.0 Sep 26, 2024
13 checks passed
@alessandroboron alessandroboron deleted the alessandro/onboarding-highlights-ship-review branch September 26, 2024 10:52
samsymons added a commit that referenced this pull request Sep 28, 2024
# By Daniel Bernal (12) and others
# Via Daniel Bernal (5) and others
* main: (46 commits)
  Release 7.139.0-4 (#3411)
  Onboarding highlights experiment updates (#3406)
  fix suggestions performance (#3405)
  For third party requests differentiate if they are affiliated with first party (#3386)
  Bump BSK to pull in C-S-S 6.19.0 (#3396)
  Release 7.139.0-3 (#3399)
  Onboarding Highlights Ship Review  (#3380)
  add assertions for tabs in suggestions (#3394)
  Release 7.139.0-2 (#3398)
  Bump BSK to Include C.S.S 6.17 (#3397)
  Bump BSK which includes C.S.S 6.17 (#3395)
  Rever BSK branch
  Revert "Bump C.S.S"
  Bump C.S.S
  translations for Switch to Tab (#3391)
  Remove Favorites section header from NTP (#3381)
  Release 7.139.0-1 (#3389)
  Add origin to /apps URL (#3378)
  chery pick returning user fix
  Release 7.138.1-0 (#3388)
  ...

# Conflicts:
#	DuckDuckGo/AppDependencyProvider.swift
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants