Thanks to visit codestin.com
Credit goes to github.com

Skip to content

docs(examples): consitent usage of self-closing tags #62165

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

AnkitaSood
Copy link
Contributor

@AnkitaSood AnkitaSood commented Jun 20, 2025

consistent usage of self-closing tags for components in all examples on this page.

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.dev application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Some of the code examples on this page are using self-closing tags for the same components while others are not.

Issue Number: N/A

What is the new behavior?

All the examples are using self-closing tags for the components.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@pullapprove pullapprove bot requested a review from AndrewKushnir June 20, 2025 15:48
Copy link
Member

@JeanMeche JeanMeche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this

@JeanMeche JeanMeche removed the request for review from AndrewKushnir June 20, 2025 16:30
@angular-robot angular-robot bot added the area: docs Related to the documentation label Jun 20, 2025
@ngbot ngbot bot added this to the Backlog milestone Jun 20, 2025
@AndrewKushnir AndrewKushnir added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release labels Jun 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker area: docs Related to the documentation area: router target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants