feat!: rename ts-check binary and add config support [skip release] #56
Conversation
This file contains hidden or 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
dsanders11
force-pushed
the
feat/generic-ts-check
branch
from
d7272da to
1af6a1a
Compare
dsanders11
force-pushed
the
feat/generic-ts-check
branch
from
1af6a1a to
4ab5491
Compare
BREAKING CHANGE: renamed electron-lint-markdown-ts-check and removed default Electron behavior, use .lint-roller.json to configure instead
dsanders11
force-pushed
the
feat/generic-ts-check
branch
from
4ab5491 to
acaf0b2
Compare
felixrieseberg
approved these changes
May 7, 2024
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
This removes all Electron-specific bits from the
markdown-ts-checkbinary so that it is generic and can be used for any project.Marking to skip release as this is part of multiple breaking changes I want to ship as a single v2, so the final PR will trigger the major release.