juxt

stijn 2017-07-26T08:59:15.805581Z

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

stijn 2017-07-26T08:59:51.820575Z

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

stijn 2017-07-26T09:01:12.855021Z

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

dominicm 2017-07-26T09:03:35.913076Z

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

stijn 2017-07-26T09:05:06.949410Z

@dominicm it does not

stijn 2017-07-26T09:05:13.952267Z

that would be an option

dominicm 2017-07-26T09:05:16.953481Z

Hmm, something takes that syntax

stijn 2017-07-26T09:05:51.966847Z

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

dominicm 2017-07-26T09:06:11.975035Z

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

stijn 2017-07-26T09:06:42.987526Z

true

stijn 2017-07-26T09:07:00.994395Z

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

stijn 2017-07-26T09:08:22.025423Z

i'm going to think about it some more

stijn 2017-07-26T09:09:48.057754Z

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

stijn 2017-07-26T09:10:51.082245Z

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

dominicm 2017-07-26T10:25:45.762426Z

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

stijn 2017-07-26T10:59:21.395604Z

ok, same status here 🙂