Skip to content

Workaround optional chaining parser bug in Angular expressions#8253

Merged
alexander-akait merged 3 commits intoprettier:masterfrom
thorn0:fix-8252
May 8, 2020
Merged

Workaround optional chaining parser bug in Angular expressions#8253
alexander-akait merged 3 commits intoprettier:masterfrom
thorn0:fix-8252

Conversation

@thorn0
Copy link
Copy Markdown
Member

@thorn0 thorn0 commented May 7, 2020

  • I’ve added tests to confirm my change works.
  • (If the change is user-facing) I’ve added my changes to changelog_unreleased/*/pr-XXXX.md file following changelog_unreleased/TEMPLATE.md.
  • I’ve read the contributing guidelines.

Try the playground for this PR

@alexander-akait alexander-akait merged commit 018a5b0 into prettier:master May 8, 2020
@thorn0 thorn0 deleted the fix-8252 branch May 8, 2020 11:29
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 9, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect formatting with safe-navigation-operator and property access via bracket-notation in angular

4 participants