Skip to content

Conversation

@quintesse
Copy link
Contributor

When one alias refers to another we now merge the attributes of the two aliases (when dealing with lists and maps, in the case of simple values the "parent" alias overrides the "child" alias).

See #1910

When one alias refers to another we now merge the attributes of the two
aliases (when dealing with lists and maps, in the case of simple values
the "parent" alias overrides the "child" alias).

See jbangdev#1910
@maxandersen
Copy link
Collaborator

I think this might be right but not fully sure ... it does seem to be breaking behavior but maybe what we had before was worse.

got some examples of what we solve and what we break?

@quintesse
Copy link
Contributor Author

It's difficult, I'm not sure how many examples we have "in the wild" of aliases referring to other aliases. And then they'd both need to have arguments (or other options) defined. Only in those cases the behaviour has been changed.

Thing is, I just tried it and although the PR does what it says it does, it unfortunately doesn't actually fix the problem mentioned in #1910 :-(

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 this pull request may close these issues.

2 participants