Closed astrale-sharp closed 1 year ago
The reason for the bug is that in rust "some text\n".lines().last() == Some("some text")
instead of ""
like I thought :grimacing:
Fixed by using .split("\n").last instead which is... a bit infuriating.
You haven't updated commit hash in the newer version. I wanted to say that in new version
it got fixed, but it's the same version with the same hash. The actual commit hash is different, though.
You haven't updated commit hash in the newer version. I wanted to say that in new
version
it got fixed, but it's the same version with the same hash. The actual commit hash is different, though.
I'm not following
Maybe something weird happened cause I just forcepushed? i forgot to squash a nitpick
This commit https://github.com/astrale-sharp/typstfmt/commit/9da3fa3fe2208532877ee4d6a906373d6b37fade and this commit https://github.com/astrale-sharp/typstfmt/commit/56fbba68fdee349691cd52b3a90afe25221588a6 have the same hash from the https://github.com/astrale-sharp/typstfmt/commit/1817538516f56bd82d89a1d560bae633beb01e48. This is a big problem right now, when you are constantly pushing new commits. The typstfmt -v
should always show the latest hash. You just forgot about it, probably. In the heat of passion.
Oh it's mostly that I only update it when releasing, which is also stupid :rofl:
I didn't yet find (look for) a good crate that does this programmatically, would be a good first issue too
I pushed a fix XD, hope it works it's hacky
I, too, think it is a hack, but it's a working one!
becomes
because content thinks it might need to break for not going over max_line_length
@Andrew15-5