-
Notifications
You must be signed in to change notification settings - Fork 27k
docs: update pipes.md example for Pipe operator precedence #58488
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
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ranjanmadhu thanks for improving Angular docs!
Could you please update the commit message (for example, using the git commit --amend command), so that it starts with docs: ? It would make the commit message aligned with the guidelines (which are enforced using the lint CI check).
|
This PR was merged into the repository by commit 940be19. The changes were merged into the following branches: main, 18.2.x, 19.0.x |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
There is an parenthesis which should not be there,
Pipe operator precedence
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information