[MBL-1164] Add post campaign fields to project queries/mutations #1965
+18
−4
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
Add two fields to the project model in graphql and in app:
-isPostCampaignEnabled
-postCampaignPledgingEnabled
🤔 Why
These fields will be used to determine if the campaign will be allowed to go into the post campaign flow (only if both are true)
🛠 How
Added the fields to the fragments for graph, added them to the model for app model
📋 QA
Check the logs on staging for these fields:
(Look up the project Baconbaconbacon on staging for a true result)
"isInPostCampaignPledgingPhase":true,"postCampaignPledgingEnabled":true,
(Most projects will be false as its not enabled creator side yet)
"isInPostCampaignPledgingPhase":false,"postCampaignPledgingEnabled":false,
Story 📖
MBL-1164