This is an issue in the markdown writer:

% pandoc -f native -s -t markdown
Pandoc (Meta {unMeta = fromList [("foo",MetaBool False)]})
[]
---
---

Gifski requires at least 2 frames in the resulting GIF, but users might accidentally trim or choose low enough FPS for the resulting GIF to contain less than 2 frames. We should show a warning in the editor's view in that case.

Right now, we just show an error when the conversion starts:

<img width="472" alt="Screen Shot 2020-10-24 at 16 53 31" src="https://user-images.githubusercontent.com/

From Cascading and Inheritance:

If a shorthand is specified as one of the CSS-wide keywords, it sets all of its sub-properties to that keyword […].

It should be probably handled by the expander decorator.

As per angularsen/UnitsNet#328 (comment)

Having a set of tests to validate that the correct abbreviation notations and symbols are used would be helpful, as we have seen from before that discrepancies tend to creep in over time.

See #328 for the (currently work in progress) guideline, go through the comments and identify what tests to write for the guid

• Guidance on adding a linter new rule-action (if none of the existing ones can perform the action, or be extended)
• Expand on guidelines re: keeping commits to logical areas of the code / individual packages where possible
• Use of conventional-commit standard going forward
• Advice not to include any package-lock.json changes PRs, for security reasons. File will be regene

Right now, we're doing a lot of this manually, and flattening the package-lock.json file. It'll save a lot (and likely protect against future breakage) to use this instead:

https://www.npmjs.com/package/npm-logical-tree