clones/sass
1
0
Fork 0
mirror of https://github.com/sass/sass.git synced 2024-09-21 02:27:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

Mark the deep-merge-order spec as accepted (#3293)

Browse Source
This commit is contained in:
Natalie Weizenbaum 2022-04-22 17:27:23 -07:00 committed by GitHub
parent c1cb057549
commit 8b5c8cf42e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 16 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

0
proposal/deep-merge-order.md → accepted/deep-merge-order.md
View File

23
spec/built-in-modules/map.md
View File

@ -25,23 +25,32 @@ deep-merge($map1, $map2)
* If `$map1` and `$map2` are not maps, throw an error.
* Let `merged` be a copy of `$map1`.
* Let `merged` be an empty map.
* For each `new-key`/`new-value` pair in `$map2`:
* For each `old-key`/`old-value` pair in `$map1`:
* If `merged` has a key `old-key` that's `==` to `new-key`:
* If `$map2` has a key `new-key` that's `==` to `old-key`:
* Let `old-value` be the value associated with `old-key` in `merged`.
* Remove `old-key`/`old-value` from `merged`.
* Let `new-value` be the value associated with `new-key` in `$map2`.
* If both `old-value` and `new-value` are maps, set `new-value` to the
result of calling `deep-merge()` with `old-value` and `new-value`.
* Associate `new-key` with `new-value` in `merged`.
* Associate `old-key` with `new-value` in `merged`.
* Otherwise, associate `old-key` with `old-value` in `merged`.
* For each `new-key`/`new-value` pair in `$map2`:
* If `merged` doesn't have key that's `==` to `new-key`, associate `new-key`
with `new-value` in `merged`.
* Return `merged`.
> Note that the order of keys in each merged map is the same as the keys in
> `$map1`, with any new keys from `$map2` added at the end in the same order
> they appear in `$map2`. This matches the ordering of the `merge()` function.
### `deep-remove()`
```