| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
Hey @masad-frost, thanks for your contribution! Please read my comment below to understand how to reorient your work to fit the design of the other plugins in this project.
Sorry, something went wrong.
|
The tests are failing on CI: > style_config = style.CreateStyleFromConfig(style_config) E NameError: name 'style' is not defined |
Sorry, something went wrong.
|
Lint caught an issue where I wasn't passing options for range formatting! |
Sorry, something went wrong.
|
Hey @masad-frost, I fixed the linting errors reported here in another PR of mine. Please let me know if you need help to fix the merge conflicts so we can merge this one. |
Sorry, something went wrong.
|
Done |
Sorry, something went wrong.
|
Hmm, not sure why lint passed locally. Hopefully this is the last of it |
Sorry, something went wrong.
There was a problem hiding this comment.
Hey @masad-frost, last review then this should be ready.
I've also seen that you have struggled a lot with our linting tests, so I'll give you a hand with them if you're unable to fix them after this review.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for your contribution @masad-frost!
Sorry, something went wrong.
|
Hey @ccordoba12, when do you plan on tagging a new release? Wondering because we wanna upgrade, also maybe i can slip #136 before then. |
Sorry, something went wrong.
|
Perhaps in a month or so. |
Sorry, something went wrong.
|
Good time to bump to 1.5? |
Sorry, something went wrong.
|
Yep, I'll release it next week. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This PR adds support for LSP formatting options https://microsoft.github.io/language-server-protocol/specifications/specification-3-17/#formattingOptions for the yapf
It adds explicit support for tabSize and insertSpaces, the rest of the options are not configurable in yapf. I did however add support for arbitrary configurations as specified in [key: string]: boolean | integer | string;.
I think this PR might break plugins as the API now passes options to formatter hooks, but not sure.
Nits are welcome as I don't normally read/write python.