Migrate to Angular v19 #414
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
michaelbromley
requested changes
Jan 3, 2025
| @@ -261,6 +261,9 @@ describe('PaginationControlsDirective:', () => { | |||
| }); | |||
| }); | |||
|
|
|||
| /** | |||
| * Test Component for testing the default controls component | |||
| */ | |||
| @@ -305,6 +309,9 @@ export class DirectiveTestComponent { | |||
| } | |||
| } | |||
|
|
|||
| /** | |||
| * Test Component for testing bounds correction logic | |||
| */ | |||
There was a problem hiding this comment.
Done, unfortunately in 2 commits (didn't realize there were two sets of duplicated comments).
|
Thx guys, any chance to be published soon ? :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First step toward standalone component version of the library.
Currently docs have been converted to standalone.
TBD migrating library source itself to standalone. Probably can pull it off by creating base class versions of applicable components and extending with skeleton module/standalone versions for users to import depending on whther or not they've gone all-in on standalone components.