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
I'm experiencing an issue with Floskell where the type-level cons operator ': is not being formatted correctly. Specifically, when I use the operator in a type signature, the apostrophe is being stuck to the preceding identifier, rather than being separated by a space.
I've tried adding the --extensions=TypeOperators flag to the Floskell configuration, but it didn't make a difference. I've also checked the Floskell documentation, but couldn't find any mention of this issue.
Here's an example of the code that's not being formatted correctly:
I'm using the Haskell.haskell extension for VS Code, which comes with Floskell as its formatting engine. I'm not sure if this issue is specific to the VS Code integration or if it's a general Floskell issue.
I'd appreciate it if someone could take a look at this issue and provide a solution or workaround. Thank you!
The text was updated successfully, but these errors were encountered:
I'm experiencing an issue with Floskell where the type-level cons operator ': is not being formatted correctly. Specifically, when I use the operator in a type signature, the apostrophe is being stuck to the preceding identifier, rather than being separated by a space.
I've tried adding the --extensions=TypeOperators flag to the Floskell configuration, but it didn't make a difference. I've also checked the Floskell documentation, but couldn't find any mention of this issue.
Here's an example of the code that's not being formatted correctly:
I'm using the Haskell.haskell extension for VS Code, which comes with Floskell as its formatting engine. I'm not sure if this issue is specific to the VS Code integration or if it's a general Floskell issue.
I'd appreciate it if someone could take a look at this issue and provide a solution or workaround. Thank you!
The text was updated successfully, but these errors were encountered: