-
Notifications
You must be signed in to change notification settings - Fork 39
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
Chained merges <<:
don’t work
#197
Comments
Fix ffdf7f5 released in 0.1.86 |
Nice one @ingydotnet, one thing remains though—so while this works now: one: &a
a: 1
two: &b
<<: *a
b: 2
three:
<<: *b (although the order of keys is reversed—which is probably a bug?) {
"one": {
"a": 1
},
"two": {
"b": 2,
"a": 1
},
"three": {
"c": 3,
"b": 2,
"a": 1
}
} This does not: one: &a
a: 1
two: &b
<<: *a
b: 2
three: *b {
"one": {
"a": 1
},
"two": {
"b": 2,
"a": 1
},
"three": {
"<<": {
"a": 1
},
"b": 2
}
} |
The key order is right afaik. Re the failing case, I suspected that when I fixed it but didn't push past your reported problem because I didn't have the time for it. I will take a look this week. Please keep the issues coming. |
Looking at this now.
compiles to:
I need to have the There's a little problem though. At this point we don't know if the key was I have an idea. I'm going to make the compiler produce
The |
@danielbayley this is fixed in the |
44f7fd5 is the fix commit, fwiw. It was quite a refactoring of how this works but I think it makes it more solid now. |
Fixed released in 0.1.87 |
Nice one @ingydotnet! Will check it out… Although, with Home Edit: I notice there already is: the |
I barely know what I'm doing with homebrew. Any help you can offer would be great. https://matrix.to/#/@ingy:yaml.io is a good way to chat with me directly if you want... |
I can take a look at the setup… As it stands, the Note
Cool, I'm really hesitant to sign up for yet another account for anything though — according to 1Password I already have well over 400! Trying to cut down… |
@ingydotnet Sure, check out #207 and yaml/homebrew-yamlscript#3! |
For example:
should produce:
but instead, produces:
The text was updated successfully, but these errors were encountered: