-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(dashpay): mock notifications #592
feat(dashpay): mock notifications #592
Conversation
@@ -22,7 +22,7 @@ NS_ASSUME_NONNULL_BEGIN | |||
|
|||
@interface DWDPNewIncomingRequestNotificationObject : DWDPNewIncomingRequestObject <DWDPNotificationItem> | |||
|
|||
- (instancetype)initWithBlockchainIdentity:(DSBlockchainIdentity *)blockchainIdentity NS_UNAVAILABLE; | |||
- (instancetype)initWithBlockchainIdentity:(DSBlockchainIdentity *)blockchainIdentity; // if !MOCK_DASHPAY NS_UNAVAILABLE; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's difficult to create a valid DSFriendRequestEntity
, so this method is the easiest way to mock a notification.
When the Platform is restored, we will search and clean up all of the MOCK_DASHPAY
-related changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Issue being fixed or feature implemented
We want to restore the Notifications flow and mock some data.
What was done?
How Has This Been Tested?
Breaking Changes
Checklist:
For repository code-owners and collaborators only