pandoc/test/command/multiple-metadata-blocks.md

If multiple blocks define a field, the first is used.

```
% pandoc -s -t native
---
foo: bar
...

---
foo: bim
...
^D
Pandoc (Meta {unMeta = fromList [("foo",MetaInlines [Str "bim"])]})
[]
```
Markdown reader: Fixed regression on left-biased union for metadata. When multiple YAML metadata blocks are used, and two define the same field, the value defined first takes precedence, according to the manual. This was changed briefly in ba3ee62323644134f2a5dd3277e3349d3681111a. This commit reverts to the original behavior and adds a test case. 2017-03-05 09:28:44 +01:00			`If multiple blocks define a field, the first is used.`

			```
			`% pandoc -s -t native`
			`---`
			`foo: bar`
			`...`

			`---`
			`foo: bim`
			`...`
			`^D`
Change merge behavior for metadata. Previously, if a document contained two YAML metadata blocks that set the same field, the conflict would be resolved in favor of the first. Now it is resolved in favor of the second (due to a change in pandoc-types). This makes the behavior more uniform with other things in pandoc (such as reference links and `--metadata-file`). 2019-11-07 19:48:38 +01:00			`Pandoc (Meta {unMeta = fromList [("foo",MetaInlines [Str "bim"])]})`
Markdown reader: Fixed regression on left-biased union for metadata. When multiple YAML metadata blocks are used, and two define the same field, the value defined first takes precedence, according to the manual. This was changed briefly in ba3ee62323644134f2a5dd3277e3349d3681111a. This commit reverts to the original behavior and adds a test case. 2017-03-05 09:28:44 +01:00			`[]`
			```