Upgrade to Angular 17

[MurhafSousli]

Installing the package causes peerDependency error

Current workaround is to add the following in the package.json file:

"overrides": {
    "mat-table-filter": {
      "@angular/cdk": ">=14.2.7",
      "@angular/material": ">=14.2.7",
      "@angular/common": ">=14.2.0",
      "@angular/core": ">=14.2.0"
    }
}

[GaneshKumarTrimble]

I also would like to know if there is a plan to upgrade this to angular 17.

[spock123]

And now 18

[Will-at-FreedomDev]

Installing the package causes peerDependency error

Current workaround is to add the following in the package.json file:

"overrides": {
    "mat-table-filter": {
      "@angular/cdk": ">=14.2.7",
      "@angular/material": ">=14.2.7",
      "@angular/common": ">=14.2.0",
      "@angular/core": ">=14.2.0"
    }
}

Cool, I didn't know that this works as a workaround to the peer dependency error (other than ignoring all peer dependencies). TBH this is a fine solution if there is no broken behavior.

I sent the author an email once in the past a while back about keeping up to date, and I got the impression that I don't think this author is planning on keeping up to date with Angular versions.

We plan on continuing to use this package until an Angular Material breaking change causes an issue some version in the future.

[jdshkolnik]

Installing the package causes peerDependency error

Current workaround is to add the following in the package.json file:

"overrides": {
    "mat-table-filter": {
      "@angular/cdk": ">=14.2.7",
      "@angular/material": ">=14.2.7",
      "@angular/common": ">=14.2.0",
      "@angular/core": ">=14.2.0"
    }
}

How does this fix anything if the later versions of Angular & Material have changed class definitions, etc.?

[Will-at-FreedomDev]

@jdshkolnik it doesn't. You should consider this project abandoned given that it isn't updated to officially support any supported Angular versions. We are planning to migrate away from this dependency when we have time or as necessary.

[Will-at-FreedomDev]

We upgraded from Angular 17 to 19 and dependency changes have rendered these workarounds obsolete. We are removing plug-in from our project.