This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-18
Channels
- # beginners (15)
- # boot (23)
- # cider (8)
- # clara (29)
- # cljs-dev (86)
- # cljsrn (36)
- # clojars (9)
- # clojure (211)
- # clojure-dusseldorf (5)
- # clojure-italy (21)
- # clojure-sg (2)
- # clojure-spec (4)
- # clojure-uk (12)
- # clojurescript (204)
- # cursive (5)
- # data-science (12)
- # datomic (15)
- # dirac (99)
- # emacs (1)
- # events (2)
- # figwheel (1)
- # fulcro (9)
- # graphql (27)
- # hoplon (50)
- # instaparse (9)
- # juxt (61)
- # keechma (6)
- # leiningen (1)
- # luminus (4)
- # lumo (24)
- # off-topic (24)
- # om (16)
- # onyx (17)
- # parinfer (35)
- # pedestal (3)
- # planck (12)
- # protorepl (8)
- # re-frame (15)
- # reagent (22)
- # ring (1)
- # rum (1)
- # spacemacs (3)
- # uncomplicate (4)
- # vim (5)
- # yada (1)
@flyboarder how come feathers over just using a cljs lib like sente?
@thedavidmeister feathers is a full community, it means we need to implement less in ClojureScript
ok, i haven't used it before actually
Also implements the web socket stuff for us, everything is either a client or server event really, the you let javelin take over
yeah, i think i've done something similar with sente
i made something castra-esque
so you can do something like
(sente.wire/send!
{:event :auth0.search/ids->profiles
:data ids
:result result}))
where result is a cell
@thedavidmeister feathers supports 6 different db’s out of the box, I can also swap the transport layer, main reasoning for using it
ah yeah
i do my own db stuff
mostly because i'm really using datascript
yeah I didnt want to lock in that portion of the stack, personally the db shouldn’t be tied to the logic
which is more like shuffling diffs around than normal REST stuff
currently [meta] builds the enterprise software for multiple startups, i needed the flexibility
@flyboarder so what's stopping us merging the 655 version bump in as 7.0.4
?
@thedavidmeister I was thinking about that, Im not sure we want to bump the clojure/clojurescript version for a patch release
@alandipert ^ thoughts?
we could just make it 7.1.0
and then your enhancements could be 7.1.1
the issue is releasing clojure 1.9.0
until its stable
we intended on holding that off as per the comment alan made
right, hmmm
the problem i have is that many other libraries are moving to spec.alpha
quite rapidly
and it's a domino effect
as soon as i use one lib with spec.alpha
then i can't use spec
based library versions
we could do a 7.1.0-SNAPSHOT
and keep that up to date
1.9.562
is the highest version i can use with spec.alpha
in it with the current hoplon
but it has bugs in it
actually there is probably over 100 fixes between 562
and 908
we could roll the fixes into hoplon to make it compatible with newer versions
but there's no way to test the fixes (i think) without also bumping the cljs version in hoplon itself
i'd be happy to roll with a snapshot for a while
actually, it seems sensible, how else will we test the changes in the wild?
sounds good, I’ll push something
awesome
it's really annoying that they changed spec
to spec.alpha
halfway through
and that spec is so useful that it is finding its way into many libraries 🙂
[hoplon "7.1.0-SNAPSHOT"]
on clojars
⚠️ This is the proposal version from PR#199
⚠️
ah awesome
i'll integrate that into my stuff sometime in the next week
very needed as i get a batch of warnings from all my if-tpl
currently 😛
@thedavidmeister I will note that some specs may have errors and fail if a value has been destructured when the spec is looking for a symbol
I think I fixed them but who knows 😛
haha i suppose i'll find out