Christopher Small
Christopher Small
Something else we could get with ids on code blocks (see #155) is linking between functions in docstrings and comments. Something like: ``` clojure ;; This is a function that...
With ids on html code elements for vars (see #155), it would be possible to automatically (optionally; opt-in) add function/var links to the table of contents. This would (I think)...
It would be great to have a link like `my.documentation.url/namespace/#my-cool-defn` to point someone to the docs for a particular function. For compilation to an uberdoc, could just be namespaced var...
Using the README as a start for documentation output could be nice for intro content. Is this out of scope?
Would be nice if marginalia could look at some attribute in project.clj for default run settings, so these don't have to be specified at the command line every time.
I have an implementation of this in Datsync ([here](https://github.com/metasoarous/datsync/blob/master/src/dat/sync/client.cljc#L437)), and I'd really rather have it just be a function in `datascript.core` if you're amenable. More or less, it creates a...
The following transaction fails in Datomic, but not DataScript: ``` [[:db/add (d/tempid :db.part/user -1) :some.ref/attr (d/tempid :db.part/user -2)]] ``` This means a little bit of extra work automatically syncing Datomic...
It would be nice to mirror more closely here.
In Datomic, if you pull `:db/id` for any eid `x` that doesn't exist, you get `{:db/id x}`. In DataScript, you get `nil`. Further, `(pull-many [:some/attr] missing-eids)` evaluates to `[]` in...
Such a protocol would make it possible to build custom connection/ref objects with special lifecycle functionality and capabilities. Right now the connections is just an atom, but it would be...