-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
fix paragraph type #1248
fix paragraph type #1248
Conversation
@davisjam not sure if this makes the |
test/specs/original/specs-spec.js
Outdated
|
||
const tokens = marked.lexer(md); | ||
|
||
expect(tokens[0].type).toBe('paragraph'); |
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.
Think this makes more sense to be in the unit tests, yeah? The construction seems similar enough and this isn't, technically speaking, checking a specific spec or the output as a whole.
@UziTech Looks OK. |
marked.parse('Hello World!'); | ||
expect(marked.parse).toHaveBeenCalled(); | ||
}); | ||
|
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.
I removed this test as well since it didn't really do anything. and was just there initially to have a test
@UziTech - looks like - is this a false positive in security check? The regexes don't seem to match what was changed. |
travis is just hung up on the security scan. this PR is good to go |
fix paragraph type
Marked version: 37c0324
Description
paragraph
becomestext
in master #1247Contributor
Committer
In most cases, this should be a different person than the contributor.