Add partial implementation for the sync endpoint.

[farodin91]

Spec

https://matrix.org/docs/spec/client_server/r0.2.0.html#get-matrix-client-r0-sync

Parameters

• [x] since
• [x] full_state
• [x] filter
• [ ] timeout
• [ ] set_presence

  State

• [x] next_batch
• [ ] presence
  • [ ] events
• [ ] rooms
  • [x] join
  • [ ] unread_notifications
  • [ ] timeline
    • [x] limited
    • [ ] prev_batch
    • [x] events (basic)
  • [ ] state
    • [ ] events
  • [ ] account_data
    • [ ] events
  • [ ] ephemeral
    • [ ] events
  • [x] leave
  • [ ] timeline
    • [ ] limited
    • [ ] prev_batch
    • [ ] events
  • [ ] state
    • [ ] events
  • [x] invite
  • [ ] invite_state
    • [ ] events

      Details

• Support partial timeline.events, timeline.limited
• No support for timeline.prev_batch
• Support following in timeline.events (m.room.member, m.room.message, m.room.history_visibility)
• Support timeline limiting by filter
• Support partial since, full_state
• Remove empty rooms rooms.join, rooms.leave, rooms.invite
• Parse all parameters since, filter, full_state, set_presence, timeout
• No support for parameter: set_presence, timeout
• Basic invalidation for parameters
• Basic macro for TryInto e.g. impl MessageEvent for Event

[jimmycuadra]

However you'd like to do it is fine. I'm OK with having only some parts of it implemented in the first PR.

[mujx]

Wouldn't be better to move the todo list into the sync issue #8 and break it into smaller ones instead of a giant PR?

[farodin91]

At this moment thought about only implement the batch system and rooms/join/account_data for the start.

[farodin91]

@mujx Could you look into?

[farodin91]

I'll split filter API in extra PR? To reduce complexity.

[jimmycuadra]

This needs the conflicts resolved once more. Sorry I've taken so long to review this! I'll get to it right away once it's ready to go.

[jimmycuadra]

🎉 🎉 🎉 Amazing work, @farodin91! 🎉 🎉 🎉