nextcloud / nextcloud/talk-ios
Use hash from capability endpoint
Open
- Dominant language
- Swift
- Stars
- 230
- Forks
- 121
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 38
Description
https://github.com/nextcloud/talk-ios/blob/46a35314f5b1c62709091cdba6c449bf8f5c350e/NextcloudTalk/NCSettingsController.m#L280-L304
Just something I noticed while I was working on federation capabilities. Right now we store the hash that lead to the hashChanged event. It would be better to use the hash that is returned in the capability call instead.
Contributor guide
Assessment
This issue has not been assessed yet.