Write a test for ParseMMDFile function.

[zeth]

I wrote tests to give full coverage for a single function. I thought I should submit it before writing a load more, find out how you like them to be done. :)

[siliconserf]

I just pinged Oliver as to whether he is no longer running this project, or even still breathing. Hoping he's just busy.

[TheJackiMonster]

If you squash the commits to one, I will merge it.

[siliconserf]

You'll have to explain that. I've not used the GitHub tool enough to interpret your comment into actions.

…

On Thu, Apr 8, 2021 at 5:44 AM Tobias Frisch ***@***.***> wrote: If you squash the commits to one, I will merge it. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#831 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHVW6FQGFGQUHJOWVVMZTIDTHWQKLANCNFSM4W7VZXGQ> .

-- *Good friends, good books and a sleepy conscience: this is the ideal life. - *Mark Twain

[TheJackiMonster]

Squashing commits is not really something Github specific. It's basically combining multiple commits into one which makes it easier maintaining a project because you don't have as much commits to select if something critical has to be reverted or something has to be looked up afterwards.

Here's a guide to squasing commits for example: https://medium.com/@slamflipstrom/a-beginners-guide-to-squashing-commits-with-git-rebase-8185cf6e62ec

It's basically using the rebase functionality of git. So you can create a commit with all changes regarding an older commit (for example the first commit of your PR) replacing those separate commits. Rebasing is also useful to make your old commits branching from the current state instead of the old state when you started a PR. So you don't have to merge multiple times creating crossings in the git graph.