[WIP] Roadmap update

[rebornix]

Yay! We love PRs! 🎊

Please include a description of your change & check your PR against this list, thanks:

• Commit message has a short title & issue references
• Each commit does a logical chunk of work.
• It builds and tests pass (e.g gulp tslint)

I'm going through the roadmap and see our current status. But I do find the warning tag a little bit confusing. It indicates the feature is partly implemented but we don't which part is missing: corner user case, test case or anything else? When we run into issues with commands in this category, we don't know whether it's a bug or a missing feature.

So here I did two things to the roadmap

1. Add 🔴 to each command that requires better description of the status: which part is missing and how current command works. Part of the commands are handled by me so I'll give them a update while rest of them are implemented by @jpoon @johnfn @xconverge @sectioneight @aminroosta ,etc. Please leave comments about the status. I'll add them to the PR and then remove the 🔴 mark.
2. Add ⬇️ to most features which rank low on our list.

After above update, we are supposed to have

1. Most commands covered, whether it's done, partially finished with detailed description, or low-pritory.
2. The rest of them will come soon.

[xconverge]

green checkmark, this is implemented

[ascandella]

I've looked over all the red circles and verified that I don't have updates. I believe I've kept the roadmap up to date with all my PRs. Will take another pass at my PRs tomorrow and verify there isn't something this PR is missing.

[rebornix]

@sectioneight thanks for your quick update :)

[xconverge]

implemented/fixed in #720

[rebornix]

@johnfn I noticed you converted the state of y{motion}, c{motion], etc from ✅ to ⚠️ , can you help me understand what's the catch there?

[rebornix]

@aminroosta you implement these features and I'm seeing them working well. Is there any hidden issue with it which makes you mark it as ⚠️ ?

[aminroosta]

@rebornix I think this is compele. But there are other low priority read only registers like command line register that are not implemented.

I've left some comments in register.ts file, I will send PR updating roadmap and adding them as low priority.

[rebornix]

Thanks for your info, I'll mark it as read only registers not supported yet first :) Then you may want to give it a better description if you like.

[johnfn]

@rebornix I think that might have been a mistake and I probably intended to mark yy and cc with ⚠️ . In any case they appear to be working now. (I was concerned about count prefixes)

I may have marked y with ⚠️ because I was concerned about undo/redo, but I'm more confident about that now, too.

[rebornix]

@johnfn thanks for the input! I just added some new icons to the roadmap and the whole idea is making the status of commands more positive and instructive. A warning is somewhat confusing as people have no idea about the expected behavior of the commands.

I added below two signs

• ✅ ⭐ telling users this command is done and it's somewhat customized with Code and we think it's better this way instead of making it totally the same as Vim.
• 🏃 It's in progress, whether there is already a PR/issue for it or it's on our task board (mine, yours, etc).

Note 🔴 will be removed once we finish the assessment of this roadmap. I'll say we are really close in some extent (comparing to competitors on other platforms) and my next step is looking into commands which are not implemented yet and see if they need more Code's ❤️ .