Space should not be added before parentheses following `?` operator

[MangelMaxime]

Issue created from fantomas-online

Code

x?a("")?b(t)

Result

x?a ("")?b (t)

Problem description

Please describe here the Fantomas problem you encountered.
Check out our Contribution Guidelines.

Extra information

• The formatted result breaks my code.
• The formatted result gives compiler warnings.
• I or my company would be willing to help fix this.
• I would like a release if this problem is solved.

Options

Fantomas main branch at 2025-03-14T18:18:01Z - 2d16ee5

Default Fantomas configuration

_{Did you know that you can ignore files when formatting by using a .fantomasignore file?
PS: It's unlikely that someone else will solve your specific issue, as it's something that you have a personal stake in.}

[nojaf]

Thank you for reporting this!
Are you interested in sending a PR for this?

[MangelMaxime]

I don't think I will have the time to investigate this issue unfortunately, I already have my hand full...

[github-actions]

🤖 This is an automated response from Repo Assist.

I've investigated this bug and submitted a fix. The root cause:

In sepSpaceBeforeParenInFuncInvocation, Expr.Dynamic (the result of a ? expression like x?a) was classified as uppercase or lowercase based on the case of the base object. When the result was used as the function of an AppSingleParenArg, the SpaceBeforeLowercaseInvocation / SpaceBeforeUppercaseInvocation settings were applied — adding an unwanted space before ("arg").

Fix: Added | Expr.Dynamic _, ParenExpr _ -> ctx in sepSpaceBeforeParenInFuncInvocation so that no space is ever inserted between a ? operator result and its parenthesised argument, regardless of configuration. All 2719 existing tests pass with this fix.

A draft PR has been opened for review.

Generated by Repo Assist

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@da02dddebe71d9a937665abdcd1f5214dab852a7