caridina

A Matrix client for Crystal matrix matrix-library
0.10.3 released

caridina 🦐

A Matrix client library written in Crystal.

It is also a species of shrimp, one of them being named "crystal red". Crystal for the language, red for the Matrix's red pill.

a crystal red shrimp

Installation

  1. Add the dependency to your shard.yml:

    dependencies:
      caridina:
        github: erdnaxeli/caridina
    
  2. Run shards install

Usage

The API documentation is available here.

Connecting

Create a new connection object:

require "caridina"

conn = Caridina::Connection.new(
  "https://my-favorite-hs.example.org",
  "my access token",
)

You can also login to get a new access token:

access_token = Caridina::Connection.login(
  "https://my-favorite-hs.example.org",
  "@mybotuserid:my-favorite-hs.example.org",
  "my secret password",
)

Sync

Now we can create a new channel, and tell the connection object to start syncing. The sync responses will be streamed in the channel.

matrix = Channel(Caridina::Responses::Sync).new
conn.sync(matrix)

sync = matrix.receive

You have now a sync response.

If you don't want to go through the whole sync response by yourself (which is understandable), we provide you a Caridina::Syncer object.

require "caridina/syncer"

syncer = Caridina::Syncer.new
syncer.on(Caridina::Events::Message) do |event|
  event = event.as(Caridina::Events::Message)
  # TODO: actually do something
end

syncer.process_response(sync)

:warning: The syncer is a new feature still in development. It currently only supports events in the joined rooms timeline. To access to other events, you need to go through the sync response.

Read event

The events in the sync response are all Caridina::Events::Event objects. You need to restrict the type of an event object to access all its fields.

sync.rooms.try &.join.each do |room_id, room|
  room.timeline.events.each do |event|
    case event
    when Caridina::Events::Member
      # someone's membership changed
    when Caridina::Events::PowerLevels
      # some authorization changed
    when Caridina::Events::Message
      # someone talked
    else
      # unknown event
    end
  end
end

Sometimes the event's content can be polymorphic too. That is especially the case for message events. By using again a case clause to event.content you can restrict its type to access all its fields.

Send events

There is not a single method to send an event. Instead this library provides a set of methods that correspond to different actions you may want to do. You usually do not need to worry about crafting the event to send.

:warning: This part is in a early stage. Only a few methods are currently provided.

# join a room
conn.join("!room_id:matrix.org")
# send a message
event_id = conn.send_message("!room_id:matrix.org", "Hello, world!")
# edit a message
conn.edit_message("!room_id:matrix.org", event_id, "Hello, world!")
# send a read receipt
conn.send_receipt("!room_id:matrix.org", "$event_id:matrix.org")
# Use the typing notification as a loader
conn.typing("!room_id:matrix.org") do
  # Do some processing.
  # While we are in the block, a typing notification will be shown on the given
  # room.
  conn.send_message("!room_id:matrix.org", "All done!")
end

Development

Install the dependencies with shards install.

  • make test runs the tests
  • make lint runs the formater plus a linter

Contributing

  1. Fork it (https://github.com/erdnaxeli/caridina/fork)
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request

Contributors

caridina:
  github: erdnaxeli/caridina
  version: ~> 0.10.3
License MIT
Crystal 0.36.1

Authors

Dependencies 0

Development Dependencies 1

  • ameba ~>0.13.2
    {'github' => 'crystal-ameba/ameba', 'version' => '~>0.13.2'}

Dependents 0

Last synced .
search fire star recently