Add autosync before local change for new and edit commands

[patrik-bartak]

Issue #, if available:
#57

Description of changes:
Currently, snippets are lost when autosync is enabled and snippets are added from different machines.
With this change, auto sync is called both before and after a new snippet is added to the local file. This means remote changes will not be overwritten.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[patrik-bartak]

To keep it simple I just copied the auto sync call before the local file is changed. The only drawback I see is that there are now two printouts. This is fine but might be confusing.

[RamiAwar]

LGTM! Simple and well-written, thanks Patrik!

Could you also look into adding tests for this if it's not too much of a hassle? The codebase is still lacking testing wise, so I try to add tests every time I touch a feature.

I don't think we have tests for sync in general yet, so it'll be a nice challenge to see how we'll mock the clients to make them testable locally! Good practice in refactoring code to make it testable.

[patrik-bartak]

Yep I can do that

[patrik-bartak]

I'm new to open source so I'm happy to practice a bit on a smaller project

[patrik-bartak]

Let's say I want to test func AutoSync(file string) that uses a sync Client. I have two options: refactor to make Client an argument, or using a mocking package like gomock. Is this right or am I missing something?

[RamiAwar]

Yes exactly. You need to parametrize these dependencies, then you'll be able to replace them with your mocks. By making Client an argument, you can then bring in our own TestClient and pass that in instead and be able to test the logic without calling a real client! I would've linked a nice article on dependency inversion and injection, but I couldn't find one that wasn't worded in a complicated way, and I think you've got the idea honestly.