lambdaisland / lambdaisland/plenish

Datomic Cloud support

Open
#17 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
56
Forks
4
PR merge metrics
No merged PRs in 30d

Description

It looks like there was some initial thought put into supporting Datomic Cloud (alias in deps.edn at least), but the current implementation is written to the Peer API and may need some work to support the Client API.

The initial issues I see are:

  • datomic.api.tx->t does not exist in the Client API
  • datomic.api.tx-range takes different args in Client API
  • datomic.Datom (used as a type hint) does not exist in the Client API

I'm happy to work on this as plenish looks like a great tool that would solve a lot of challenges for my team.

Would you be open to having support for Datomic Cloud in the project?

And since it looks like you started with Datomic Cloud, any major gotchas or challenges I should watch out for?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Datomic Cloud alias in deps.edn and compare the current Peer API usage with the Client API. Review datomic.api.tx->t, datomic.api.tx-range, and the datomic.Datom type hint; done means the listed Client API incompatibilities are addressed and Datomic Cloud support works.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
database
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.