Support shimmed ruby versions

[hrabe]

The plugin currently only works, if in shimmed environment (e.g. rbenv / asdf) the global ruby version it the same as within the project. If global ruby version is something like 2.7.0 it fails within vscode format on save.

This is due to starting the ruby interpreter (spawn) within drives root folder, which falls back to global ruby version instead of project used one.

The fix sets the working dir for spawned ruby process to the directory, where the file to be formatted is contained.
This will automatically use the correct shimmed ruby version of the project or falls back (if no shim has been used) to global ruby version.

This also may make the .editorconfig obsolete.

[bschlenk]

yess, thank you! I've been banging my head against the wall trying to upgrade a large codebase to prettier 3, and this was the last blocker. Just tried your fix locally and it works

[kddnewton]

Hey @hrabe - I think this makes sense to me. Happy to merge, but let's make sure we get CI green first. You should be able to rebase off main to get the latest fixes, and then if this becomes green I can merge it.

[kddnewton]

Just marking this as "request changes"

[hrabe]

@kddnewton all tests locally running well now.

[kddnewton]

@hrabe it looks like everything is failing on CI with this PR. Any chance it's unable to find the correct bundle now that the cwd is changing? Are you able to replicate locally?

[hrabe]

@kddnewton Now using the cwd only if file is given. Now clue how to reproduce CI issue, cause yarn run test / npm run test works locally. Assume, that test doesn't give a file and default process.cwd is than in root without bundled gem.
Would love to see the tests on CI now.

[hrabe]

@kddnewton do you think we could bump a new version?