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

chore(2631): Refactor storage service to separate channel and message logic #2713

Merged
merged 10 commits into from
Feb 4, 2025

Conversation

islathehut
Copy link
Collaborator

@islathehut islathehut commented Jan 27, 2025

Pull Request Checklist

  • I have linked this PR to a related GitHub issue.
  • I have added a description of the change (and Github issue number, if any) to the root CHANGELOG.md.

(Optional) Mobile checklist

Please ensure you completed the following checks if you did any changes to the mobile package:

  • I have run e2e tests for mobile
  • I have updated base screenshots for visual regression tests

@islathehut
Copy link
Collaborator Author

#2631

@islathehut islathehut marked this pull request as ready for review January 27, 2025 17:56
@islathehut islathehut changed the base branch from develop to 4.0.0 January 28, 2025 17:25
@islathehut islathehut changed the base branch from 4.0.0 to develop February 4, 2025 19:37
@islathehut islathehut force-pushed the feat/2631-message-channel-storage-refactor branch from 645ccb1 to 03cf584 Compare February 4, 2025 20:06
@islathehut islathehut requested a review from adrastaea February 4, 2025 20:35
Copy link
Collaborator

@adrastaea adrastaea left a comment

Choose a reason for hiding this comment

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

One nitpick of user facing behavior, but may be out of scope for this pr

try {
return await this.getStore().add(encryptedMessage)
} catch (e) {
throw new CompoundError(`Could not append message (entry not allowed to write to the log)`, e)
Copy link
Collaborator

Choose a reason for hiding this comment

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

This may be existing behavior, but when we hit this error, the message is still displayed in the timeline (grayed out as you might expect for an unsent message, but when you close and reopen the app, it is no longer grayed out which is misleading as to whether it was actually sent)

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yea that's existing behavior we need to deal with. We can't know if a message has been sent or not right now, as far as I know.

@islathehut islathehut merged commit 2490750 into develop Feb 4, 2025
26 of 29 checks passed
islathehut added a commit that referenced this pull request Feb 4, 2025
… logic (#2713)

* Create channels service and small fix for loading chain on app start

* Separate logic further into channelstore and messagesservice

* Add temp placeholders for encryption/decryption

* Minor clean up

* Expand messages service, tweak getting messages, fix/add tests

* Fix subscribing not getting old messages on join

* Fix peer list not updating

* Add compounderror

* Update auth

* Update CHANGELOG.md
islathehut added a commit that referenced this pull request Feb 7, 2025
… logic (#2713)

* Create channels service and small fix for loading chain on app start

* Separate logic further into channelstore and messagesservice

* Add temp placeholders for encryption/decryption

* Minor clean up

* Expand messages service, tweak getting messages, fix/add tests

* Fix subscribing not getting old messages on join

* Fix peer list not updating

* Add compounderror

* Update auth

* Update CHANGELOG.md
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.

2 participants