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`
Use pretty-simple to format native output. Previously we used our own homespun formatting. But this produces over-long lines that aren't ideal for diffs in tests. Easier to use something off-the-shelf and standard. Closes #7580. Performance is slower by about a factor of 10, but this isn't really a problem because native isn't suitable as a serialization format. (For serialization you should use json, because the reader is so much faster than native.) 2021-09-19 21:09:51 +02:00			`Pandoc`
Switch from pretty-simple to pretty-show for native output. Update tests. Reason: it turns out that the native output generated by pretty-simple isn't always readable by the native reader. According to https://github.com/cdepillabout/pretty-simple/issues/99 it is not a design goal of the library that the rendered values be readable using 'read'. This makes it unsuitable for our purposes. pretty-show is a bit slower and it uses 4-space indents (non-configurable), but it doesn't have this serious drawback. 2021-09-29 06:17:53 +02:00			`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			```