Code health

A lot of things have moved recently, and the project has had several major refactors since the beginning. As such, the code could be much cleaner. Once more tests are added and we can ensure large changes don’t lead to regressions, I’d like to do the following things:

• Find a general convention for defining variables (making wrappers around registerCommand or utility functions called from several registerCommands).
• Better name commands, with more descriptive categories and a more obvious mapping between command name and source file name in src/commands.ts.
• Clean up extension.ts.
• Reorder imports in all files.

[yuchenshi]

@71 How do you feel about cutting a release after #101 is merged? I think we’ve got the most low-hanging fruits and we can get more help to find more edge cases if a new version is released.

Also, FYI I imagine objects in caret-based selections is the largest source of bugs. There are tons of edge cases and we don’t have great coverage. I’ve written extensive tests for character-based and used it manually for a while, but not carets. We can also put that in known issues and call for help.

[71]

@tshort We were planning on releasing the update on the marketplace but ended up working on other things for a while. Now we’re trying to fix issues that won’t be too much work and release that on the marketplace, since there haven’t been too many issues with master.

And glad to know you like it! I’ve been running it daily without issues for a few weeks, but since I’m not a power user myself either, I was worried there would be issues in the parts I rarely use.