[MBL-703] Prelaunch Page Watch Count Update #1813
Merged
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
We noticed that prelaunch page watch count was not being accurately update after saving/unsaving the project.
🤔 Why
Matching Android functionality. Also makes more sense to show the new follower count after following a project.
🛠 How
Modified the
.graphql
files forUnwatch
andWatch
project to includewatchesCount
.Updated the envelope to have this property after getting it back from the mutation data.
The
PledgeStateCTAType
has a new property within theprelaunch
enum case forwatchesCount
.We merge the new pledge state with
watchesCount
to thewatchesCountText
inPledgeCTAContainerViewViewModel
which was previously just using the project it was configured with for that text.All the other signals/notifications should be the same, it's just about keeping track of the
watchesCount
after the network response returns forunwatchProject
andwatchProject
.👀 See
Before 🐛
RPReplay_Final1681320063.MP4
After 🦋
RPReplay_Final1681319958.MP4
✅ Acceptance criteria