6f088bb5c5
In some instances the communities migration would be skipped but not marked as `dirty`. This commit addresses the issue by: - Making sure that if dirty is set the migration is not skipped but replayed - If the version is on the communities migration and dirty is false, we check for the presence of the communities table. If not present we replay the communities migration. - Make community_id field in user_messages nullable It also removes all the `down` migration, as we can't use them effectively, as explained in the README.md added. |
||
|---|---|---|
| .. | ||
| audio | ||
| common | ||
| communities | ||
| datasync | ||
| encryption | ||
| identity | ||
| images | ||
| internal/sqlite | ||
| migrations | ||
| protobuf | ||
| pushnotificationclient | ||
| pushnotificationserver | ||
| sqlite | ||
| subscription | ||
| transport | ||
| tt | ||
| urls | ||
| v1 | ||
| zaputil | ||
| LICENSE | ||
| README.md | ||
| chat.go | ||
| chat_group_proxy.go | ||
| chat_test.go | ||
| communities_messenger_test.go | ||
| contact.go | ||
| emoji_reaction.go | ||
| ens.go | ||
| ens_test.go | ||
| errors.go | ||
| group_chat_invitation.go | ||
| group_chat_system_messages.go | ||
| message_builder.go | ||
| message_handler.go | ||
| message_handler_test.go | ||
| message_persistence.go | ||
| message_validator.go | ||
| message_validator_test.go | ||
| messenger.go | ||
| messenger_config.go | ||
| messenger_contact_update_test.go | ||
| messenger_emoji_test.go | ||
| messenger_installations_test.go | ||
| messenger_mute_test.go | ||
| messenger_response.go | ||
| messenger_response_test.go | ||
| messenger_test.go | ||
| persistence.go | ||
| persistence_test.go | ||
| push_notification_test.go | ||
| transaction_validator.go | ||
| transaction_validator_test.go | ||
README.md
status-go/protocol
This is an implementation of the secure transport and payloads which are a part of the Status Client specification.
This implementation uses SQLite and SQLCipher for persistent storage.
The payloads are encoded using protocol-buffers.
Content
messenger.gois the main file which exportsMessengerstruct. This is a public API to interact with this implementation of the Status Chat Protocol.protobuf/contains protobuf files implementing payloads described in the Payloads spec.encryption/implements the Secure Transport spec.transport/connects the Status Chat Protocol with a wire-protocol which in our case is either Whisper or Waku.datasync/is an adapter for MVDS.applicationmetadata/is an outer layer wrapping a payload with an app-specific metadata like a signature.identity/implements details related to creating a three-word name and identicon.migrations/contains implementation specific migrations for the sqlite database which is used byMessengeras a persistent data store.
History
Originally this package was a dedicated repo called status-protocol-go and was migrated into status-go. The new status-go/protocol package maintained its own dependencies until sub modules were removed and the root go.mod file managed all dependencies for the entire status-go repo.