Fork me on GitHub
#juxt
<
2017-07-26
>
stijn08:07:15

not sure if this would be possible, but in aero, would it make sense to create some kind of 'hierarchy' of profiles?

stijn08:07:51

the use case is that some profiles have a lot in common: e.g. individual developer machine vs. cloud instances (dev, staging, prod)

stijn09:07:12

whereas now, there's only one default profile from which all other profiles 'inherit'

dominicm09:07:35

@stijn does #{:dev :staging} work in #profile

stijn09:07:13

that would be an option

dominicm09:07:16

Hmm, something takes that syntax

stijn09:07:51

this might actually be a good use case for keyword inheritance 🙂

dominicm09:07:11

yeah. although the problem with inheritance is that it's non-obvious.

stijn09:07:00

you could setup the inheritance from a profiles.edn file or so though

stijn09:07:22

i'm going to think about it some more

stijn09:07:48

another unrelated question: would it be interesting to create lacinia-yada like lacinia-pedestal? I have most of it done, but need to extract into a library

stijn09:07:51

I understood from @jonpither that juxt is also using lacinia, so maybe you have something already?

dominicm10:07:45

we do have something already, yep 🙂. But not as a lib, we just throw it together where we needed.

stijn10:07:21

ok, same status here 🙂