refactor(@angular-devkit/schematics): remove UpdateBuffer and rename UpdateBuffer2 to UpdateBuffer#24035
Conversation
|
I was unsure whether to directly delete the UpdateBuffer. If you think it's ok to remove, then I will do that and update it with a breaking change description. I will also remove the |
|
Should I also merge |
No, as |
UpdateBuffer and rename UpdateBuffer2 to UpdateBuffer
|
|
alan-agius4
left a comment
There was a problem hiding this comment.
Thanks for your contribution. One comment about the LinkedList otherwise LGTM
…e `UpdateBuffer2` to `UpdateBuffer` This PR removes the internally built `UpdateBuffer` and renames `UpdateBuffer2` (based on magic-string) to `UpdateBuffer`. This should have little to no impact for consumers. BREAKING CHANGE: The depracated `UpdateBuffer` has been removed and `UpdateBuffer2` is renamed to `UpdateBuffer`. With this change the related and deprecated symbols `ContentCannotBeRemovedException` and `Chunk` have also been removed.
Upstream UpdateBuffer change has been merged (angular/angular-cli#24035) which allows us to remove the UpdateBuffer patching.
|
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. |
This PR removes the internally built
UpdateBufferand renamesUpdateBuffer2(based on magic-string) toUpdateBuffer. This should have little to no impact for consumers.BREAKING CHANGE:
The depracated
UpdateBufferhas been removed andUpdateBuffer2is renamed toUpdateBuffer. With this change the related and deprecated symbolsContentCannotBeRemovedExceptionandChunkhave also been removed.PR Checklist
Please check to confirm your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The deprecated UpdateBuffer instance is being used per default.
Issue Number: N/A
What is the new behavior?
The magic-string based UpdateBuffer2 is being used per default.
Does this PR introduce a breaking change?
Other information
See #21209 and #21110