Skip to content

Fix to set vfile.value if a vfile@5 is given#143

Merged
wooorm merged 2 commits intov9from
value
Jul 1, 2021
Merged

Fix to set vfile.value if a vfile@5 is given#143
wooorm merged 2 commits intov9from
value

Conversation

@wooorm
Copy link
Copy Markdown
Member

@wooorm wooorm commented Jul 1, 2021

Initial checklist

  • I read the support docs
  • I read the contributing guide
  • I agree to follow the code of conduct
  • I searched issues and couldn’t find anything (or linked relevant results below)
  • If applicable, I’ve added docs and tests

Description of changes

vfile@5 changed from the contents to the value field. Given that not all of the ecosystem has updated yet, and that some version mismatches will occur for the foreseeable future, setting both contents*and*value` in those cases will hopefully alleviate
some of the struggles with updating.

Related to remarkjs/remark-frontmatter#16.

wooorm added 2 commits July 1, 2021 10:38
vfile@5 changed from the `contents` to the `value field.
Given that not all of the ecosystem has updated yet, and that some
version mismatches will occur for the foreseeable future, setting
both `contents` *and* `value` in those cases will hopefully alleviate
some of the struggles with updating.

Related to remarkjs/remark-frontmatter#16.
@codecov-commenter

This comment has been minimized.

@wooorm wooorm merged commit bc50a01 into v9 Jul 1, 2021
@wooorm wooorm deleted the value branch July 1, 2021 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants