Invalid front-matter should not be cached #166
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In case of an error, the result should not be cached. Currently the second call with the same invalid contents returns a (wrong) value.
Bumping the thread. As of today, using version "4.0.3", the bug still exists: invalid front-matter are cached, which break scenario where code using gray-matter is re-run several times.