[NT-451] Contact Creator Flow #912
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cdolm92
commented
Oct 25, 2019
| .ignoreValues() | ||
| self.goToContactCreator = project | ||
| .takeWhen(self.menuOptionSelectedSignal.filter { $0 == .contactCreator }) | ||
| .map { project in (MessageSubject.project(project), .backerModal)} |
There was a problem hiding this comment.
What should the correct tracking context be for this screen? Should I add a new context to the MessageDialogContext?
…contact-creator-flow
ifbarrera
approved these changes
Oct 28, 2019
…contact-creator-flow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
User can now contact the creator.
🤔 Why
Backers can get questions regarding their pledge/rewards answered by creators.
👀 See
✅ Acceptance criteria
Contact creator, you should see the message creator screen w/ the creator's name.