Skip to content
This repository was archived by the owner on Dec 1, 2024. It is now read-only.

Replace remark with hallmark#621

Merged
vweevers merged 3 commits intomasterfrom
replace-remark-with-hallmark
Nov 24, 2018
Merged

Replace remark with hallmark#621
vweevers merged 3 commits intomasterfrom
replace-remark-with-hallmark

Conversation

@vweevers
Copy link
Copy Markdown
Member

Squash on merge. Closes #614, closes #615, closes #620.

The third commit adds a lot of diff noise, because hallmark has a custom list item indent option. Should we remove that from hallmark? With remark defaults, lists look like this (two spaces):

-  foo
-  bar

With hallmark they look like (single space):

- foo
- bar

Comment thread package.json
]
"hallmark": {
"community": "level-community",
"validateLinks": false
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added this temporary validateLinks option to hallmark because we have a lot of HTML anchors (<a>) in the levelup README, and remark does not parse those, leading to many lint failures.

Comment thread CONTRIBUTORS.md
| **James Halliday** | [**@substack**](https://github.com/substack) | [**@substack@twitter**](https://twitter.com/substack) |
| **David Björklund** | [**@kesla**](https://github.com/kesla) | [**@david_bjorklund@twitter**](https://twitter.com/david_bjorklund) |
| **Jake Verbaten** | [**@Raynos**](https://github.com/Raynos) | [**@raynos@twitter**](https://twitter.com/raynos) |
| **Raynos** | | |
Copy link
Copy Markdown
Member Author

@vweevers vweevers Nov 24, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This must be caused by some change between remark-git-contributors 0.2.1 and 0.3.0, but IMO it's not important to fix now.

@vweevers vweevers merged commit 1b50636 into master Nov 24, 2018
@vweevers vweevers deleted the replace-remark-with-hallmark branch November 24, 2018 20:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants