| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-03-30 | Prevent null issues when strings are unequal (#290) | Ellis KenyĆ | |
| In the case where s2 is larger than s1, this errors because the index is out of range. A good testcase is the below ```lisp (apheleia--align-point " <div class=\"left-[40rem] fixed inset-y-0 right-0 z-0 hidden lg:block xl:left-[50rem]\">\n <svg\n" "<div class=\"left-[40rem] fixed inset-y-0 right-0 z-0 hidden lg:block xl:left-[50rem]\">\n <svg" 6) ``` If I've implemented the indexing wrong, do let me know but this seems to work just fine now for `mix` (the formatter that triggered this) --------- Co-authored-by: Radon Rosborough <radon@intuitiveexplanations.com> | |||
| 2023-11-05 | Add support for formatters locally installed via yarn 2+ pnp mode (#200) | Ed Slocomb | |
| This adds support for formatters installed locally in project directories via yarn 2's "zero install" [pnp mode](https://yarnpkg.com/features/pnp). It's quite similar to the support for formatters installed locally in a project's `node_modules` via npm, and leverages the `npx` symbol, so existing formatter definitions should work without modification. This checks for a `.pnp.cjs` file (expected in the project root for yarn pnp projects), then looks for a yarn executable, and checks the version of yarn to make sure it supports pnp. If that works, we just push `"yarn"` onto the front of `command`. I've only tested this with a locally installed `prettier.js`. It's very much a works-for-me draft, I'm putting in a PR to make sure this is a workable approach before going any further with it. --------- Co-authored-by: Radon Rosborough <radon@intuitiveexplanations.com> | |||
| 2022-01-05 | Add formatter tests (#72) | Radon Rosborough | |
| Closes #24 Builds on #25 by @PrimaryCanary | |||
| 2022-01-03 | Port longlines checker from CTRLF | Radon Rosborough | |
