not sure if this would be possible, but in aero, would it make sense to create some kind of 'hierarchy' of profiles?
the use case is that some profiles have a lot in common: e.g. individual developer machine vs. cloud instances (dev, staging, prod)
whereas now, there's only one default profile from which all other profiles 'inherit'
@stijn does #{:dev :staging}
work in #profile
@dominicm it does not
that would be an option
Hmm, something takes that syntax
this might actually be a good use case for keyword inheritance 🙂
yeah. although the problem with inheritance is that it's non-obvious.
true
you could setup the inheritance from a profiles.edn file or so though
i'm going to think about it some more
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
I understood from @jonpither that juxt is also using lacinia, so maybe you have something already?
we do have something already, yep 🙂. But not as a lib, we just throw it together where we needed.
ok, same status here 🙂