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(typing): send typing indicator events - epic (WP-4590) #2127

Merged
merged 5 commits into from
Oct 11, 2023

Conversation

yamilmedina
Copy link
Contributor


PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

Issues

Collection of small PRs that brings alive the sending typing indicator, plus some refactor on the receiving part to make it more stable, testable and mantainable.

The PRs already reviewd.

Testing

Test Coverage (Optional)

  • I have added automated test to this contribution

PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

…-4590) (#2118)

* fix: exclude selfuser from typingevents

* fix: exclude selfuser from typingevents

* fix: coverage for flag check

* chore: api configuration for sending typing status

* chore: api configuration for sending typing status v0

* chore: api configuration for sending typing status v0

* chore: pr comments

* feat: mapper and repo ops

* feat: mapper and repo ops

* feat: mapper and repo ops

* chore: detekt

* chore: detekt

* chore: tests broken

* feat(typing): send typing indicator events use case and cleanup code pt2. (WPB-4590) (#2121)

* feat: mapper and repo ops deletion

* chore: ip

* chore: some fun refactoring, just ideas

* chore: some fun refactoring, just ideas

* chore: some fun refactoring, just ideas

* chore: working base

* chore: clear indicators

* chore: clear indicators

* chore: clear indicators

* chore: notes

* chore: refactor into new classes splitted

* chore: comments cleanup

* chore: detekt fixes

* Empty-Commit

* feat(typing): send typing indicator event tests pt3. (WPB-4590) (#2122)

* chore: test cov

* chore: test cov

* chore: test cov

* chore: test cov

* chore: test cov
@yamilmedina yamilmedina changed the title feat(typing): send typing indicator events networking layer - epic (WP-4590) feat(typing): send typing indicator events - epic (WP-4590) Oct 10, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 10, 2023

Unit Test Results

   442 files  +3     442 suites  +3   2m 21s ⏱️ +6s
2 400 tests +9  2 296 ✔️ +9  104 💤 ±0  0 ±0 

Results for commit 33597cc. ± Comparison against base commit fa037c3.

♻️ This comment has been updated with latest results.

@datadog-wireapp
Copy link

datadog-wireapp bot commented Oct 10, 2023

Datadog Report

All test runs 1103ea5 🔗

2 Total Test Services: 0 Failed, 0 with New Flaky, 2 Passed

Test Services
Service Name Failed Known Flaky New Flaky Passed Skipped Wall Time Branch View
kalium-ios 0 0 0 1807 44 6m 25.1s Link
kalium-jvm 0 0 0 2295 104 10m 56s Link

Copy link
Contributor

@gongracr gongracr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Beautiful and clean implementation 🌺 Awesome Job Yamil👷 👏

userTypingCache.block { entry ->
entry.clear()
}.also {
userTypingDataSourceFlow.tryEmit(Unit)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why we are using tryEmit if we are not checking the result value?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is so we can make the Observers of userTypingDataSourceFlow collect the new state. Since we are relying on this flow to get new map userTypingCache states to consumers.

@yamilmedina yamilmedina added this pull request to the merge queue Oct 11, 2023
Merged via the queue into develop with commit c923de5 Oct 11, 2023
17 checks passed
@yamilmedina yamilmedina deleted the epic/sending-typing-events branch October 11, 2023 11:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants