Add edit and view changes features

mikeebowen commented 3 years ago

This pull request adds 2 new features:

User can edit xml parts in VS Code and those changes will be reflected in the OOXML document. E.G. if a user edits a .docx file in VS Code the changes will be reflected when the document is opened in Word or another document editor.
After editing from an outside program, xml parts that have been changed will be reflected with a yellow asterisk for edited, a green asterisk for created, and a red asterisk for deleted. If a file has been changed the user can right click for the context menu and click "Compare with Previous" to view a diff of the previous version of the xml part and the current version.
Tests have been added for the new features.
Documentation in the README has been updated to show users how to user the new features.

yuenm18 commented 3 years ago

Thank you for the PR, it looks like these changes will be very useful

I have a couple of general comments:

I noticed an issue when you click a folder in the "OOXML Viewer." It opens up the first file in the folder rather than just opening the dropdown
Lets make the next version 1.0.0 and have the changelog file contain only the original entry for version 0.0.1 and a new entry for version 1.0.0 with all your changes since version 0.0.1 because the extension only has version 0.0.1 published
Lets get rid of the releases folder, I want to tag the commit that the version was built off of and add the vsix file to corresponding the github release rather than committing the visx files
Can you add an extra newlines between your methods

mikeebowen commented 3 years ago

Thanks for the suggestions, obviously .toString() is not asynch 🤦‍♂️.

I will look into the folder displaying a file.
I can remove the tags and revert to v1.0.0
I need to keep the releases folder for now, because some coworkers are dog fooding the extension to help me find bugs and that is how I give them the releases. I don't have any objection to you deleting it after the pull request is approved before publishing, though.
I can add extra new lines.
I used a cli tool called auto-changelog to create the changelog. It works really well, but because I ran it on my fork it lists all the commits as from my fork. After the pull request is approved, you should rerun auto-changelog so the changelog has the correct links to the commits in your repo. I will try and have an updated pull request for you tomorrow or the next day. I'll keep you posted.

mikeebowen commented 3 years ago

OK, the remaining issues have been taken care of

Stopped calling viewFile when the user clicks on a FileNode that is a folder
Reverted the versions and it now goes from v0.0.1 to v1.0.0 and the CHANGELOG.md has been updated with auto-changelog
Deleted the releases folder, I can distribute the vsix other ways
Added lines between the methods

Hopefully that takes care of everything 🙂