Fix Add Blank Line After YAML
Only Working When YAML Already Exists
#1200
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1188
Relates to #1199
There was an issue with running the Linter rule
Add Blank Line after YAML
where it was not adding a blank line after the YAML if it was added by sayYAML Timestamp
. The issue was caused by the YAML being added long after the rule had run. This meant it could not add the blank line. To fix this, the rule needs to run beforeYAML Timestamp
if the YAML is present since there could be a modification that needs to cause a timestamp update. However if there is no YAML frontmatter present, then it can run afterYAML Timestamp
since it will either create the frontmatter or no frontmatter will exist by the time the Linter's rules run.There was also a change to make the release compiled version of the plugin be
16.x
since that is the minimum version that should be supported by plugins at this time.There was also a small fix of a typo in a setting's wording.
It also adds a fix to the minification of the styles which was previously not merged due to the gitignore.
Changes Made:
Add Blank Line After YAML
either before or afterYAML Timestamp
depending upon the situation in question