fix: Lint tag-data.json when regenerated during dev/build step #1093
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.
Issue
When
tag-data.jsonis automatically regenerated it doesn't follow the formatting of the repo. This leads to the local file differing from the upstream file every time the dev server is run.Changes
Before:
{"markdown":1,"code":1,"features":1,"next-js":6,"math":1,"ols":1,"github":1,"guide":5,"tailwind":3,"hello":1,"holiday":1,"canada":1,"images":1,"feature":2,"writings":1,"book":1,"reflection":1,"multi-author":1}After:
{ "markdown": 1, "code": 1, "features": 1, "next-js": 6, "math": 1, "ols": 1, "github": 1, "guide": 5, "tailwind": 3, "holiday": 1, "canada": 1, "images": 1, "feature": 2, "writings": 1, "book": 1, "reflection": 1, "multi-author": 1 }