NT-1821: Switch prelaunch display logic to use display_prelaunch field from v1 API #1205
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📲 What
Switch logic tied to
prelaunchActivated()
from theUser
payload to rely ondisplayPrelaunch()
instead.🤔 Why
Currently, native is using the field
prelaunch_activated
to determine the display logic of prelaunch deeplinks. We want to change this logic to checkdisplay_prelaunch
instead.The backend will be updating
prelaunch_activated
to actually return the correctproject.prelaunch_activated
value. This is also keeping parity with web as they are using this field. Because of this, any instances using prelaunch_activated for display logic will need to be updated to use display_prelaunch instead.Relevant backend PR: https://github.com/kickstarter/kickstarter/pull/21408
🛠 How
User
struct to grabdisplayPrelaunch
value available from the APIprelaunchActivated()
todisplayPrelaunch()
so logic relys on this booleanProjectFactory
methodprelaunchProject
to be set thedisplayPrelaunch
value📋 QA
This change requires smoke and regression testing.
Story 📖
NT-1821: Switch prelaunch display logic to use display_prelaunch field from v1 API