Surfingkeys 1.0

I’m refactoring the project and will release 1.0 hopefully. The goal is to

• integrate with neovim with native messaging.
• settle down the public APIs for setting snippets and document them.
• improve the build process with webpack.
• add unit tests.
• remove the Mermaid diagram generator, which is unnecessary for the extension.

So no more feature requests or bugs will be addressed for current release 0.9.74. The code change is big, and will need some little change in your setting snippets, but there will be no impact if you’re a basic user which means you don’t customize setting with snippets. As said, the code change is big, I can not provide the expected date of arrival now.

For anyone who is interested with the neovim integration, please see Use neovim in Google Chrome / Chromium through Surfingkeys - YouTube for how it works.

Thanks for your attention.

[brookhong]

@aspiers Thanks a lot for you great suggestions, all of them make sense.

Sorry for the confusion, though such chaos is expected and I had pined this issue for mitigation almost 3 months ago, it did make me nervous when it came, as so many people are impacted, not to mention those related issues here, there are also messages coming from different channels such as email, review comments on web store and personal IM.

The root cause is that I haven’t designed those public APIs well from the very beginning, which exposed too much internal implementations and made settings snippets uncontrollable and unexpectable, and that is why it is the second goal of this refactoring.

Some hot fix is pending review on Chrome Web store now, hopefully it will fix some missing/broken APIs and make error message explicit that it is from Surfingkeys.

[Stvad]

FF version does not seem to be updated? I have a shared config, and I expect if I update it’d break the things in FF that runs the older version