You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
It's easy to make a formatting error to the yaml front matter that goes unnoticed until all journal commands start failing due to a parsing error. I recently encountered this problem because I had manually written a readme tag as a yaml array rather than as a scalar value.
To address this situation, all cmdlets should catch all entries that cannot be correctly parsed and display a list to the user. The list should include the file path of the entry, the error, and instructions to fix.
The text was updated successfully, but these errors were encountered:
Summary
It's easy to make a formatting error to the yaml front matter that goes unnoticed until all journal commands start failing due to a parsing error. I recently encountered this problem because I had manually written a
readme
tag as a yaml array rather than as a scalar value.To address this situation, all cmdlets should catch all entries that cannot be correctly parsed and display a list to the user. The list should include the file path of the entry, the error, and instructions to fix.
The text was updated successfully, but these errors were encountered: