Skip to content
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

Merged
merged 13 commits into from
Jan 29, 2024

Conversation

Elyniss
Copy link
Contributor

@Elyniss Elyniss commented Jan 26, 2024

No description provided.

@Elyniss Elyniss requested review from kacperoak, jakubuid, Talhaali00 and a team as code owners January 26, 2024 16:24
Copy link

github-actions bot commented Jan 26, 2024

Qodana Community for Android

57 new problems were found

Inspection name Severity Problems
Constant conditions 🔶 Warning 42
Serializable object must implement 'readResolve' 🔶 Warning 10
Control flow with empty body 🔶 Warning 1
JUnit malformed declaration 🔶 Warning 1
Constant conditions ◽️ Notice 2
Argument could be converted to 'Set' to improve performance ◽️ Notice 1
View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

  1. Register at Qodana Cloud and configure the action
  2. Use GitHub Code Scanning with Qodana
  3. Host Qodana report at GitHub Pages
  4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/[email protected]
        with:
          upload-result: true
Contact Qodana team

Contact us at [email protected]


onNotifyDeleteResponseUseCase.events
onDeleteResponseUseCase.events
.filter { it.first == params }
.map { it.second }
Copy link
Contributor

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?

Copy link
Contributor Author

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

@Elyniss Elyniss merged commit ab3f487 into develop Jan 29, 2024
15 checks passed
@Elyniss Elyniss deleted the feat/notify/notification_history branch January 29, 2024 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants