Skip to content

Conversation

@jkillian
Copy link
Contributor

@jkillian jkillian commented Mar 8, 2019

What this PR does / why we need it:
As an alternative to #3525, we should at least specify that you need VSCode 1.31.0 or newer in order for the extension to run correctly. (In all reality, I should've done this with the original CamelCaseMotion PR, but unfortunately overlooked that it was a possibility.)

This sadly won't help people who are having trouble with 1.1.0. Ideally we could unpublish that one release and the release 1.1.1 with this change included. But not sure if that's possible.

@jpoon
Copy link
Member

jpoon commented Mar 8, 2019

In all reality, I should've done this with the original CamelCaseMotion PR, but unfortunately overlooked that it was a possibility.

Yah, I hadn't realized there was a dependency on a particular vscode version. Oh well, live and learn.

@jpoon jpoon merged commit 6ff07f4 into VSCodeVim:master Mar 8, 2019
@jkillian jkillian deleted the patch-1 branch March 9, 2019 07:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants