Skip to content
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

New: Add recommended config (fixes #151) #153

Merged
merged 1 commit into from
Aug 2, 2020
Merged

New: Add recommended config (fixes #151) #153

merged 1 commit into from
Aug 2, 2020

Conversation

btmills
Copy link
Member

@btmills btmills commented Jul 18, 2020

Should plugin:markdown/recommended enable the processor on just .md files or also .mkdn, .mdown, and .markdown (the same file extensions as v1)? I went with just .md since overriding to add the other extensions is straightforward, but I could be convinced to include the other three.

Is test coverage adequate? I My thinking was that asserting "it works" is sufficient to say the recommended config is being loaded, and the rest of the plugin tests can handle the details.

@btmills btmills changed the title Add recommended config (fixes #151) New: Add recommended config (fixes #151) Jul 18, 2020
@btmills btmills marked this pull request as draft July 19, 2020 04:11
@btmills btmills marked this pull request as ready for review July 19, 2020 23:05
@btmills btmills mentioned this pull request Jul 19, 2020
Copy link
Member

@kaicataldo kaicataldo left a comment

Choose a reason for hiding this comment

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

Starting with .md makes sense to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants