Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • M metaolm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Archive
  • metaolm
  • Issues
  • #1
Closed
Open
Issue created Sep 05, 2018 by Johannes Hayeß@jhaye🖤Maintainer

Split json_object module

Currently the json_object module contains all structs that are used for serialisation/deserialisation.

They can be categorised as follows:

  • Identity key pair of an olm_rs::account::OlmAccount
  • Device keys for uploading to the Matrix server, as described here
  • One-time-keys for uploading to the Matrix server, as described here

The amount of JSON objects that will have to be used together with serde will only increase as the project continues, so splitting them seems like a good idea to me.

Assignee
Assign to
Time tracking