@jdneo Thank you for bumping leetcode-cli to 2.8.0! Do you mind publish that change to npmjs as well? So I can specify the new version in package.json. Or do you prefer to specify the commit hash in package.json?

@dzz007 you can first use the latest bit of the cli and link it to the vs code extension locally. Let me know if everything works fine. After that I'll release it to the registry.

@jdneo thank you for responding! I just tested with locally installing with master branch of leetcode-cli in vscode-leetcode. Everything works fine, I checked both the leetcode.com and leetcode-cn.com endpoints.
The only problem I found is that changing Endpoint in vscode-leetcode's setting page actually doesn't work. But that is a separate bug which is not related to this leetcode-cli upgrade at all, and I verified that because it exists in the current version as well.

Just published 2.8.0.

@jdneo Thanks, just finished changing package.json & package-lock.json. I tested again and it works well.

The content of package-lock.json looks strange, why the entries have node_modules prefix?

I believe it's because I am currently using NPM v7 which introduced some changes to the lock file as specified in "lockfileVersion": 2. I can downgrade to NPM v6 and regenerate the lock file if you want.

Just a sidenote, IIRC v2 version of the lock-file is backward compatible with older version of NPM. So it should be able to work fine with NPMv6 for example.

ok, thanks for the information

@jdneo no problem! Do you want me to keep the lock file as-is or do you want or to use the old version?

If it's backward compatible, then it's fine I think.

Thank you for your review! I just added the application scope.

Coule you add a tsdoc for the showSolution function notifying the param needTranslation will not take effect?

@jdneo That's a good point! I will add it in couple hours. Do you want me to put it in leetCodeExecutor?

Thanks!

Apologize for lazy merge. I just get the permission to merge the PRs. 😃