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

Alias Merge Order #23

Open
axrs opened this issue Mar 4, 2020 · 0 comments · May be fixed by #26
Open

Alias Merge Order #23

axrs opened this issue Mar 4, 2020 · 0 comments · May be fixed by #26

Comments

@axrs
Copy link
Contributor

axrs commented Mar 4, 2020

We have a parent project that has several aliases pre defined.
In the child project, we really wanted to change how an alias was run. What we found was that the parent aliases took prescedence.

For example:

...
; Parent
:aliases {"lint-nsorg" ["nsorg" "--replace"]}
...

...
; Child
:aliases {"lint-nsorg" ["nsorg"]
          "new-alias" ["preserved"]}
...

; Produces
:aliases {"lint-nsorg" ["nsorg" "--replace"]
          "new-alias" ["preserved"]}

I feel like the child aliases should be merged last to allow overriding aliases. For example: (merge grand-parent parent child)

Frozenlock added a commit to Frozenlock/lein-parent that referenced this issue Jun 22, 2020
@Frozenlock Frozenlock linked a pull request Jun 22, 2020 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant