You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for reporting this. Indeed, I can reproduce this and Topiary actually fails with this input, because the idempotency constraint is flaunted (Nickel must disable this).
That record which gets expanded (and ultimately fails) is on a single line, so I would expect no changes to the original input. If it were to span multiple lines, I would expect something like:
Previously, a line break was prepended to _any_ `=` sign within an
`annotated_assignment` scope. This was too liberal, if `=` signs
appeared within annotations themselves.
Resolves#680
* Nickel: Line break only before binding = in annotations
Previously, a line break was prepended to _any_ `=` sign within an
`annotated_assignment` scope. This was too liberal, if `=` signs
appeared within annotations themselves.
Resolves#680
* Nickel: Remove `annotated_assigment` scope as now redundant
Describe the bug
To Reproduce
I write this
Turns into this after a
nickel format
Which then turns into this after a second
nickel format
Expected behavior
I expect no changes to happen.
Environment
Additional context
This is stable
The text was updated successfully, but these errors were encountered: