Boost platform targets minds#4030
Ticket(s) / Related Merge Requests
Summary of Changes
Added 3 new boolean fields to boosts in the boosts table:
target_platform_web
target_platform_android
target_platform_ios
Validation checking: If the feature flag is ON and a newly-created boost has set values for all three platforms, we throw an error if all three are false.
After the mysql-provision commands are run, all pre-existing boosts will have TRUE values for all three of the new fields. New boosts created after this is merged will be stored with TRUE values for all three of the new fields (even if the flag is off). In other words, the only way any of these three fields will be stored with anything other than TRUE is if the boost creator has manually deselected a checkbox, thereby making that target platform FALSE.
Testing Considerations
Creating boosts - feature flag on and flag off.
Deployment Considerations
minds-4030-boost-platform-targeting feature flag must be on.
mysql tables need new columns (see mysql-provision.sql file)
ALTER TABLE boosts
ADD target_platform_web boolean DEFAULT true
AFTER target_suitability;
ALTER TABLE boosts
ADD target_platform_android boolean DEFAULT true
AFTER target_platform_web;
ALTER TABLE boosts
ADD target_platform_ios boolean DEFAULT true
AFTER target_platform_android;
These changes affect the mobile team and they should be informed.
Regression Scope
Boosts
Platform Affected (web, mobile, etc)
Web, mobile
Developer Testing Completed
Screenshots / Screen Recording
Does this impact
-
Localization -
Dark/light mode -
Guest mode
Definition of Done Checklist
-
The Acceptance Criteria has been met -
Code is tested: Testing includes unit/spec, E2E/automated and manual testing -
Merge requests description has been filled out