Skip to content

exercises/markdown: add extensive header parsing tests#1817

Merged
angelikatyborska merged 1 commit intoexercism:mainfrom
gsilvapt:ft-markdown_improved_tests
Jul 17, 2021
Merged

exercises/markdown: add extensive header parsing tests#1817
angelikatyborska merged 1 commit intoexercism:mainfrom
gsilvapt:ft-markdown_improved_tests

Conversation

@gsilvapt
Copy link
Copy Markdown
Contributor

@gsilvapt gsilvapt commented Jul 2, 2021

As discussed in issue #1812, markdown exercise would benefit with more
extensive tests to ensure learners write dynamic code, capable of
handling all header depths there is.
To ensure their code is not too dynamic, I added the h7 level. It does
not exist in the HTML specification and therefore should be equal to the
input.

Resolves #1812.

Comment thread exercises/markdown/canonical-data.json Outdated
Comment thread exercises/markdown/canonical-data.json Outdated
Comment thread exercises/markdown/canonical-data.json Outdated
Copy link
Copy Markdown
Member

@ErikSchierboom ErikSchierboom left a comment

Choose a reason for hiding this comment

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

Looks good! I have a minor cosmetic remark: the new tests use a different indentation from the existing files. @gsilvapt could you use the same indentation (2 spaces) for the new test cases?

@gsilvapt
Copy link
Copy Markdown
Contributor Author

Looks good! I have a minor cosmetic remark: the new tests use a different indentation from the existing files. @gsilvapt could you use the same indentation (2 spaces) for the new test cases?

Thank you very much! Absolutely, yes. Seems some tests below were also wrongly indented so I took the opportunity and fixed those too.

Comment thread exercises/markdown/canonical-data.json Outdated
As discussed in issue #1812, markdown exercise would benefit with more
extensive tests to ensure learners write dynamic code, capable of
handling all header depths there is.
To ensure their code is not too dynamic, I added the h7 level. It does
not exist in the HTML specification and therefore should be equal to the
input.

Resolves #1812.
@angelikatyborska
Copy link
Copy Markdown
Member

three approvals = merge 🙂

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[markdown] Update header test to work from h1 to h6

4 participants