-
Notifications
You must be signed in to change notification settings - Fork 26.1k
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
fix(core): preserve comments in internal inject migration #60588
Conversation
The internal-only combineMemberInitializers option for the inject migration sometimes dropped the doc comments from the members.
``, | ||
`@Directive()`, | ||
`class MyDir {`, | ||
` private foo = inject(Foo);`, |
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.
My code here loses the whitespace (e.g., blank lines) around the members, which isn't ideal. Let me know if you know of a good way to preserve it.
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.
Since this is internal-only and we apply auto-formatting, I think it's okay.
``, | ||
`@Directive()`, | ||
`class MyDir {`, | ||
` private foo = inject(Foo);`, |
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.
Since this is internal-only and we apply auto-formatting, I think it's okay.
The internal-only combineMemberInitializers option for the inject migration sometimes dropped the doc comments from the members. PR Close #60588
This PR was merged into the repository by commit 0cd7d3b. The changes were merged into the following branches: main, 19.2.x |
The internal-only combineMemberInitializers option for the inject migration sometimes dropped the
doc comments from the members.
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