Fork me on GitHub
#hoplon
<
2017-08-18
>
thedavidmeister02:08:41

@flyboarder how come feathers over just using a cljs lib like sente?

flyboarder02:08:02

@thedavidmeister feathers is a full community, it means we need to implement less in ClojureScript

thedavidmeister02:08:17

ok, i haven't used it before actually

flyboarder02:08:25

Also implements the web socket stuff for us, everything is either a client or server event really, the you let javelin take over

thedavidmeister02:08:08

yeah, i think i've done something similar with sente

thedavidmeister02:08:05

i made something castra-esque

thedavidmeister02:08:13

so you can do something like

thedavidmeister02:08:16

(sente.wire/send!
  {:event :auth0.search/ids->profiles
   :data ids
   :result result}))

thedavidmeister02:08:21

where result is a cell

flyboarder02:08:31

@thedavidmeister feathers supports 6 different db’s out of the box, I can also swap the transport layer, main reasoning for using it

thedavidmeister02:08:45

i do my own db stuff

thedavidmeister02:08:09

mostly because i'm really using datascript

flyboarder02:08:17

yeah I didnt want to lock in that portion of the stack, personally the db shouldn’t be tied to the logic

thedavidmeister02:08:20

which is more like shuffling diffs around than normal REST stuff

flyboarder02:08:27

currently [meta] builds the enterprise software for multiple startups, i needed the flexibility

thedavidmeister04:08:04

@flyboarder so what's stopping us merging the 655 version bump in as 7.0.4?

flyboarder04:08:06

@thedavidmeister I was thinking about that, Im not sure we want to bump the clojure/clojurescript version for a patch release

thedavidmeister04:08:53

we could just make it 7.1.0 and then your enhancements could be 7.1.1

flyboarder04:08:56

the issue is releasing clojure 1.9.0 until its stable

flyboarder04:08:35

we intended on holding that off as per the comment alan made

thedavidmeister04:08:08

the problem i have is that many other libraries are moving to spec.alpha

thedavidmeister04:08:45

and it's a domino effect

thedavidmeister04:08:12

as soon as i use one lib with spec.alpha then i can't use spec based library versions

flyboarder04:08:50

we could do a 7.1.0-SNAPSHOT and keep that up to date

thedavidmeister04:08:10

1.9.562 is the highest version i can use with spec.alpha in it with the current hoplon

thedavidmeister04:08:40

but it has bugs in it

thedavidmeister04:08:54

actually there is probably over 100 fixes between 562 and 908

thedavidmeister04:08:32

we could roll the fixes into hoplon to make it compatible with newer versions

thedavidmeister04:08:46

but there's no way to test the fixes (i think) without also bumping the cljs version in hoplon itself

thedavidmeister04:08:32

i'd be happy to roll with a snapshot for a while

thedavidmeister04:08:46

actually, it seems sensible, how else will we test the changes in the wild?

flyboarder04:08:05

sounds good, I’ll push something

thedavidmeister04:08:21

it's really annoying that they changed spec to spec.alpha halfway through

thedavidmeister04:08:36

and that spec is so useful that it is finding its way into many libraries 🙂

flyboarder05:08:00

[hoplon "7.1.0-SNAPSHOT"] on clojars ⚠️ This is the proposal version from PR#199 ⚠️

thedavidmeister05:08:01

i'll integrate that into my stuff sometime in the next week

thedavidmeister05:08:22

very needed as i get a batch of warnings from all my if-tpl currently 😛

flyboarder05:08:32

@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

flyboarder05:08:51

I think I fixed them but who knows 😛

thedavidmeister05:08:28

haha i suppose i'll find out