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 the Privacy Pro status attribute matcher #3033

Merged
merged 2 commits into from
Jul 4, 2024

Conversation

samsymons
Copy link
Contributor

Task/Issue URL: https://app.asana.com/0/1199333091098016/1207731341550989/f
Tech Design URL:
CC:

Description:

This PR updates the Privacy Pro status attribute matcher to accept an array.

On the client side, it also makes it so that the active case no longer also targets expiring users. If we want to target both active and expiring users, we can do so by specifying multiple cases in the array.

Steps to test this PR:

  1. This attribute was originally reviewed in Add additional RMF attributes #2949 and is covered by unit tests, just check that the changes make sense and that BSK tests have passed

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

@samsymons samsymons requested a review from ayoy July 3, 2024 23:02
privacyProIsActive = true
privacyProIsExpiring = true
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We no longer match multiple statuses for expiring users, as we can now match multiple statuses at once using an array in the RMF manifest.

Copy link
Contributor

@ayoy ayoy left a comment

Choose a reason for hiding this comment

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

LGTM 👍

samsymons added a commit to duckduckgo/BrowserServicesKit that referenced this pull request Jul 4, 2024
Required:

Task/Issue URL: https://app.asana.com/0/1199333091098016/1207731341550989/f
iOS PR: duckduckgo/iOS#3033
macOS PR: duckduckgo/macos-browser#2940
What kind of version bump will this require?: Patch (technically the public API has not changed)

Description:

This PR updates the Privacy Pro status attribute to match an array instead of a string.
@samsymons samsymons merged commit cd76085 into main Jul 4, 2024
14 checks passed
@samsymons samsymons deleted the sam/update-ppro-status-attribute branch July 4, 2024 09:00
samsymons added a commit that referenced this pull request Jul 7, 2024
# By Christopher Brind (3) and others
# Via Anh Do (1) and GitHub (1)
* main:
  Add connection tester failure pixels (#3049)
  Release 7.127.0-1 (#3051)
  fix bug not clearing ui properly on autoclear (#3050)
  widget UI tests (#3042)
  fix autofill widget failure (#3040)
  macOS BSK change: De-duplicate passwords on import (#3048)
  Privacy Dashboard refactor (#3038)
  Make Maestro tests fail on flow cancellation (#3036)
  Improve VPN logging logic (#3032)
  Subscription refactoring #5 (#3023)
  Update Sync error pixels (#3046)
  Fixes App Data Clearing State Status In Settings (#3041)
  update sync error copy (#2870)
  Fixes for Xcode 16 (BSK -> 164.3.0) (#3035)
  Update the Privacy Pro status attribute matcher (#3033)

# Conflicts:
#	DuckDuckGo.xcodeproj/project.pbxproj
#	DuckDuckGo.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved
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