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
Currently a function call with a callback as the final argument will be formatted neatly with all args on one line save for the function body, thanks to @giacomocavalieri's great work:
wibble("value",fn(attr){attr
|> ...})
Request
I'd like this formatting applied consistently to tuple construction also:
#("value",fn(attr){attr
|> ...})
鈽濓笍 currently the above formats like this 馃憞
#("value",fn(attr){attr
|> ...},)
Context
In lustre component definitions must supply a dictionary of attribute names to listen to and a decoder to run when those attributes change:
The recent formatter changes have made lots of common lustre code much more legible but this particular aspect produces quite a lot of vertical noise. For non-trivial components that may want to listen to more than one or two attributes this can end up occupying a lot of space in a module.
The text was updated successfully, but these errors were encountered:
Background
Currently a function call with a callback as the final argument will be formatted neatly with all args on one line save for the function body, thanks to @giacomocavalieri's great work:
Request
I'd like this formatting applied consistently to tuple construction also:
鈽濓笍 currently the above formats like this 馃憞
Context
In lustre component definitions must supply a dictionary of attribute names to listen to and a decoder to run when those attributes change:
The recent formatter changes have made lots of common lustre code much more legible but this particular aspect produces quite a lot of vertical noise. For non-trivial components that may want to listen to more than one or two attributes this can end up occupying a lot of space in a module.
The text was updated successfully, but these errors were encountered: