Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clip/Aero Reference Alignment #36

Open
jvia opened this issue Apr 13, 2023 · 1 comment
Open

Clip/Aero Reference Alignment #36

jvia opened this issue Apr 13, 2023 · 1 comment

Comments

@jvia
Copy link

jvia commented Apr 13, 2023

Using Clip and Aero in combination has been a great experience so far. The only UX issue I run into on my team is the difference between how Clip and Aero refer to other pieces of the edn config. It could be nice to have alignment or a doc example on how to create align on a per-project basis.

Here are some examples, one with alignment on the Clip syntax and the other with alignment on the Aero syntax. I suspect the Aero syntax would be achievable on a per-project basis by defining custom reader tags.

clip

{:configuration
 {:port 300}

 :components
 {:database  {:start (some.ns.database/start)}
  :webserver {:start (some.ns.webserver/start
                      {:port     (aero/ref :port)
                       :database (clip/ref :database)})}}}

aero

{:configuration
 {:port 300}

 :components
 {:database  {:start (some.ns.database/start)}
  :webserver {:start (some.ns.webserver/start
                      {:port     #aero/ref :port
                       :database #clip/ref :database})}}}
@SevereOverfl0w
Copy link
Collaborator

One downside I've noticed when there's alignment is that people get confused about when to use which. Having the two syntaxes might help delineate the two kinds of reference, unsure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants