This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-24
Channels
- # announcements (3)
- # beginners (128)
- # boot (2)
- # braveandtrue (97)
- # calva (13)
- # cider (4)
- # cljdoc (12)
- # cljs-dev (16)
- # clojure (78)
- # clojure-germany (8)
- # clojure-italy (5)
- # clojure-nl (1)
- # clojure-spec (59)
- # clojure-uk (29)
- # clojurescript (46)
- # core-async (9)
- # cursive (63)
- # data-science (3)
- # datomic (22)
- # devcards (1)
- # duct (7)
- # emacs (4)
- # flambo (2)
- # fulcro (37)
- # instaparse (6)
- # jobs-discuss (38)
- # juxt (1)
- # off-topic (35)
- # om-next (1)
- # parinfer (7)
- # re-frame (14)
- # reagent (6)
- # reitit (21)
- # rum (1)
- # shadow-cljs (74)
- # spacemacs (8)
- # specter (1)
- # sql (3)
- # testing (2)
- # unrepl (2)
- # yada (6)
Are there any plans for allowing clj files as migrations? Similar to rails for example. The clj files could be completely sideeffectful and return nothing, but be tracked through the same hashing-id mechanism. We have complex fixtures/seeds at our company and having programmatic migrations has been on our minds for a while to implement.
This wouldn’t be too hard to implement. You’d just need to write a init-key
that returns a record that satisfies the ragtime.protocols/Migration
protocol.
Or a collection of records if you wanted.
and maybe this https://github.com/mariusz-jachimowicz-83/duct-migrations-auto-cfg if you want load migrations from folder rather than describing them one by one