feat: Angular v.20 update#644
Conversation
|
@mauriciovigolo Hi, I created this PR to update the library with the new Angular 20, could you review this please ? |
|
Looks like you have some formatting changes in the commits. Might want to remove those since they are not relevant to this pull request. |
Thanks, done |
|
Related issue #645 |
|
Just updated the @angular-eslint packages to v20. @mauriciovigolo Can this PR be merged ? I've been using v19 of this library with Angular 20 and it works fine, so a new version should be ok. Problem is right now i'm forced to use npm install --force just for this library so it's not convenient :( |
|
Hi @ArnaudFlaesch, |
Thanks a lot to you, your library is awesome :) |
mauriciovigolo
left a comment
There was a problem hiding this comment.
Great work!
Thank you @ArnaudFlaesch 💯
6d0a7bb
into
mauriciovigolo:feature/angular-v20-update
|
Thanks, just made a quick change here : #649 to fix the lint issue |
* feature: Angular v.20 update (#644) * docs: fix typos in v19 migration guide (#629) * docs: fix incorrect migration guide URL (#639) Co-authored-by: luca.gobbi <luca.gobbi@niuma.it> * docs: fix add missing intercept import in README (#638) * fix: Replace constructor parameter injection with inject() function (#649) * feature: add a new example, improved docs and versions. - Add a new project for fetching the configuration file hosted externally. - Updated libraries version. - Updated the documentation and added information about the auto refresh token feature. --------- Co-authored-by: Arnaud Flaesch <ArnaudFlaesch@users.noreply.github.com> Co-authored-by: Radoš Milićev <40705899+rammba@users.noreply.github.com> Co-authored-by: Luca Gobbi <80841205+lucagobbi@users.noreply.github.com> Co-authored-by: luca.gobbi <luca.gobbi@niuma.it> Co-authored-by: Bart van Beusekom <bartvanbeusekom@gmail.com>
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?