-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
cannot determine if Expr AppSingleParenArg Fantomas.Core.SyntaxOak+ExprAppSingleParenArgNode is uppercase or lowercase #3088
Comments
A workaround this problem is to split the operation into several intermediate variables. |
Would accept a PR for this. |
I still seem to get this error |
Can you reproduce via online tool? |
Strange. I can't reproduce it with online tool. But when using 7.0.1 in Fabulous.AST with the following test: [<Fact>]
let ``AppSingleParenArg expression``() =
Oak() {
AnonymousModule() {
AppSingleParenArgExpr(
DynamicExpr(
AppSingleParenArgExpr(
DynamicExpr(AppSingleParenArgExpr(DynamicExpr("x", "a"), ParenExpr("")), "b"),
ParenExpr("t")
),
"b"
),
ParenExpr("t")
)
}
}
|> produces
"""
x?a("")?b(t)?b(t)
""" |
The online tool doesn't produce |
Adding spacing on this line change the meaning of the code. Instead of being a chain of property/method chain, it becomes calls to method. For example, here is the result of Fable compilation even if this apply to normal F# code too I believe. let test : obj = x?a("")?b(t)?b(t)
let test2 : obj = x?a ("")?b (t)?b (t) export const test = ((x().a("")).b(t)).b(t);
export const test2 = x().a("".b, t.b, t); |
Feel free to open an issue for that. |
Note
I could not use Fantomas tool report this error because Github was complaining about the URL being too long but the code is already minimal (just a few characters)
I tried to manual respect the issue template
Related to #3086
Code and expected
Result
Fantomas crash with
Problem description
Fantomas is crashing
Extra information
Options
Fantomas v6.3.3+ccaee4a0756c8bc6f6717ae603915f6f5c52b09a
The text was updated successfully, but these errors were encountered: