-
Notifications
You must be signed in to change notification settings - Fork 87
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: Notifications History with changed ids #1288
Conversation
Qodana Community for Android57 new problems were found
View the detailed Qodana reportTo be able to view the detailed Qodana report, you can either:
To get - name: 'Qodana Scan'
uses: JetBrains/[email protected]
with:
upload-result: true Contact Qodana teamContact us at [email protected]
|
protocol/notify/src/main/kotlin/com/walletconnect/notify/client/NotifyProtocol.kt
Outdated
Show resolved
Hide resolved
protocol/notify/src/main/kotlin/com/walletconnect/notify/common/model/EngineMapper.kt
Show resolved
Hide resolved
protocol/notify/src/main/kotlin/com/walletconnect/notify/engine/NotifyEngine.kt
Show resolved
Hide resolved
|
||
onNotifyDeleteResponseUseCase.events | ||
onDeleteResponseUseCase.events | ||
.filter { it.first == params } | ||
.map { it.second } |
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.
Can't .filter and .map be included in onDeleteResponseUseCase?
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.
No because they need to match request params. They could be other delete responses happening at time of collecting
No description provided.