Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reader tagged literals result in incorrect alignment #110

Closed
axelarge opened this issue Oct 9, 2024 · 1 comment
Closed

Reader tagged literals result in incorrect alignment #110

axelarge opened this issue Oct 9, 2024 · 1 comment
Labels
bug Something isn't working v1 blocker Required for a v1.0.0 release

Comments

@axelarge
Copy link

axelarge commented Oct 9, 2024

Please see screenshot:

CleanShot 2024-10-09 at 12 59 44@2x

Input:

(-> #js [(one-promise)
         (another-promise)]
    (js/Promise.all)
    (.then (fn [_])))

(-> #uuid "15adfdf0-2e6b-410e-a489-f71d1dd17642"
    str)

I would expect the code to be unchanged after formatting, but everything gets aligned to one character after #

(-> #js [(one-promise)
         (another-promise)]
     (js/Promise.all)
     (.then (fn [_])))

(-> #uuid "15adfdf0-2e6b-410e-a489-f71d1dd17642"
     str)

I would guess that this is also what's causing #108.

@axelarge axelarge changed the title Reader literals result in incorrect alignment Reader tagged literals result in incorrect alignment Oct 9, 2024
@oakmac oakmac added bug Something isn't working v1 blocker Required for a v1.0.0 release labels Oct 11, 2024
@oakmac
Copy link
Owner

oakmac commented Oct 12, 2024

Fixed with PR-118

@oakmac oakmac closed this as completed Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v1 blocker Required for a v1.0.0 release
Projects
None yet
Development

No branches or pull requests

2 participants