-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore/issue 43 linting for markdown and JSON #102
Merged
thescientist13
merged 9 commits into
main
from
chore/issue-43-eslint-markdown-json-linting
Oct 4, 2024
Merged
chore/issue 43 linting for markdown and JSON #102
thescientist13
merged 9 commits into
main
from
chore/issue-43-eslint-markdown-json-linting
Oct 4, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thescientist13
added
chore
project maintenance related tasks
enhancement
New feature or request
labels
Oct 4, 2024
✅ Deploy Preview for super-tapioca-5987ce ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
thescientist13
added
content
Non Greenwood specific content like home page copy text, blog posts, etc
and removed
enhancement
New feature or request
labels
Oct 4, 2024
thescientist13
commented
Oct 4, 2024
CONTRIBUTING.md
Outdated
@@ -121,6 +122,7 @@ For interactive components that would require client side interactivity, like ev | |||
```js | |||
import sheet from "./card.css" with { type: "css" }; | |||
|
|||
const hello = world(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops! this was just a test, need to remove this lol
interestingly, this example doesn't actually seem to trigger an error though? It's ripped right from the README though... 🤔
thescientist13
changed the title
linting for markdown and JSON
chore/linting for markdown and JSON
Oct 4, 2024
thescientist13
changed the title
chore/linting for markdown and JSON
chore/issue 43 linting for markdown and JSON
Oct 4, 2024
thescientist13
force-pushed
the
chore/issue-43-eslint-markdown-json-linting
branch
from
October 4, 2024 22:14
32983cb
to
361c348
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related Issue
resolves #42 and #43
Summary of Changes
TODO
no-undef
set to0
🤦♂️