refactor: rename addMarkdownHighlighter to setMarkdownHighlighter (Fixes #3105) #3879
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
|
• setMarkdownHighlighter() replaces addMarkdownHighlighter() for clearer intent and naming consistency. 💬 Why this matters: |
|
Can you resolve the merge conflicts, @Subham-KRLX ? |
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.
Description
This PR updates the Markdown syntax highlighter API for greater clarity and consistency:
✨ Introduced setMarkdownHighlighter() — a clearer, more intuitive method name.
📚 Updated README.md to reflect the new API and include a note about the deprecation.
🧪 Added a new AVA test (user-config-deprecation.test.js) to verify both backward compatibility and warning output.
✅ All existing tests pass successfully. No example configuration updates are required.
✅ Closes [#3105]