Added condition for '+' case.

[t-mangoe]

Description

this PR fixes the issue #13018

Fix #13018

Checklist

• I’ve added tests to confirm my change works.
• (If changing the API or CLI) I’ve documented the changes I’ve made (in the docs/ directory).
• (If the change is user-facing) I’ve added my changes to changelog_unreleased/*/XXXX.md file following changelog_unreleased/TEMPLATE.md.
• I’ve read the contributing guidelines.

✨Try the playground for this PR✨

[t-mangoe]

I am not sure how to update the test, so, if the test needs to be updated, I would appreciate knowing how to update it.
Also, if there are any other areas that need correction, please let me know.

[sosukesuzuki]

@t-mangoe Thank you for working on this! I've pushed a commit to add tests. If you will contribute to Prettier again, please add tests with to refer my commit.

[fisker]

should we also do the same to ~ and ++?

[sosukesuzuki]

node.operator.length <= 2 ?

[fisker]

node.operator.length <= 2 ?

No, just add the UpdateExpression and list operators.

[t-mangoe]

@fisker
Thank you for your comment. I added processing for UpdateExpression case. Also, I grouped the target operators into targetUnaryExpressionOperators and targetUpdateExpressionOperators.
With these responses, how do you like it?

[fisker]

I assume we are going to treat a++ the same, please add test for it.

[t-mangoe]

I added tests for a++ and a--.

[fisker]

Looks good to me, thank you!

[fisker]

Also, I grouped the target operators into targetUnaryExpressionOperators and targetUpdateExpressionOperators.

Sorry, missed this.

I'd use

const simpleOperators = new Map([
	'UnaryExpression', new Set(['!', '-', '+', '~']),
	// To prevent unexpected operators add in future
	'UpdateExpression', new Set(['++', '--']),
]);

if (simpleOperators.has(node.type) && simpleOperators.get(node.type).has(node.operator)) {
  // ...
}