* return date object from date/datetime widgets if no format set
BREAKING CHANGE
As of 1.0, the documented behavior for the date and datetime widgets was
to always return a string value, but they were instead returning a date
object if the default date was not manually changed by the user. This
was addressed in #1143, but it became clear afterward that static site
generators were depending on the raw date objects that Netlify CMS was
unintentionally producing. Remaining as is or addressing the bug were
both "breaking" states, so this commit reverts to producing raw date
objects when no format is explicitly set.
It is now considered an edge case to require string dates, as most
static site generators expect to parse a raw date against formatting in
a site's templates.
Also note that this commit improves the original behavior by always
providing a date object when no format is provided, even if the user
manually changes the value.
* produce raw date when no format is provided
* fix: allows for valid config types expansion
* feat: config url can now come through link tag
* fix: lints added coded
* fix: slims down code per review
* fix: expands query to find supported type
* fix: removes typo in test copy
* fix: changes validTypes to object
* fix: groups config functions into one getConfig func
* adds console message for config url
* adds to docs
* update docs
* fix test
* fix merge conflicts
contributor addition moved to #1241
* avoids empty path with link without href. changes link console message
* removes additional console
* fixes link path in console
* fix: remove superfluous .allcontributorsrc change
* document config option to hide preview by default
* document config option to hide preview pane by default
* revise wording to specify preview disables entirely for a collection
* adjust wording of editor section to be more consistent with other settings
sections
* add note about defaulting to true
* frontmatter functions now exported as curried constructors
* changed formats.js to accomodate frontmatter.js changes
* can only use custom delimiters if format is specified
* reverting changes
* updated tests to reflect changes
* created tests for custom delimiters
* updated docs to reflect addition of custom delimiter configuration
* formatByExtension no longer takes custom delimiter
* missed some formatByExtension calls
* Edited the docs according to suggestions
* Throws an error if a custom delimiter is set without declaring frontmatter format
* Throws error if custom delimiter set without explicit and proper frontmatter format being declared
* example config file set to proper defaults
* moved frontmatterFormats to formats
* Update .all-contributorsrc
* updated contributions
* Clarify docs
* Format JSON files.
Currently we store JSON as a single line in files. We should prettify it
like we do the other formats.
* Add output parsers to the frontmatter list.
* Cleanup frontmatter format parser options.
* Support writing frontmatter in TOML and JSON.
Right now we can read TOML or JSON frontmatter by inferring,
but we can only write frontmatter in YAML. This change allows the
frontmatter format to be explicitly set for reading and writing.
* Fix frontmatter formatter.
* Update Frontmatter formatter tests.
* Update frontmatter format docs.
