-
Notifications
You must be signed in to change notification settings - Fork 3.5k
fix:ambiguity around extensions #3787
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
Open
DewminK
wants to merge
3
commits into
markedjs:master
Choose a base branch
from
DewminK:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+357
−18
Open
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,44 @@ | ||
| import { marked } from './src/marked.ts'; | ||
|
|
||
| // Test that both property names work | ||
| const testExtension = { | ||
| name: 'test', | ||
| level: 'inline', | ||
| start(src) { return src.indexOf('TEST'); }, | ||
| tokenizer(src) { | ||
| const match = src.match(/^TEST/); | ||
| if (match) { | ||
| return { | ||
| type: 'test', | ||
| raw: match[0], | ||
| text: 'TESTED' | ||
| }; | ||
| } | ||
| }, | ||
| renderer(token) { | ||
| return `<span class="test">${token.text}</span>`; | ||
| } | ||
| }; | ||
|
|
||
| // Test old property name (should still work) | ||
| console.log('Testing old property name (extensions):'); | ||
| try { | ||
| marked.use({ extensions: [testExtension] }); | ||
| console.log('✓ Old property name works'); | ||
| console.log('Result:', marked.parse('This is TEST content')); | ||
| } catch (e) { | ||
| console.log('✗ Old property name failed:', e.message); | ||
| } | ||
|
|
||
| // Reset marked | ||
| marked.setOptions(marked.getDefaults()); | ||
|
|
||
| // Test new property name | ||
| console.log('\nTesting new property name (tokenizerAndRendererExtensions):'); | ||
| try { | ||
| marked.use({ tokenizerAndRendererExtensions: [testExtension] }); | ||
| console.log('✓ New property name works'); | ||
| console.log('Result:', marked.parse('This is TEST content')); | ||
| } catch (e) { | ||
| console.log('✗ New property name failed:', e.message); | ||
| } | ||
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.
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.
While the current test correctly validates both property names by resetting the global
markedinstance, this approach of mutating and resetting global state can make tests brittle and harder to maintain. A better practice for test isolation is to use separateMarkedinstances for each test case. This avoids side effects between tests and makes them more robust. The suggested change refactors the test to use this approach, and also updates the import statement accordingly.