-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
Angular 6 Support #23
Comments
I think this is a great idea, and I would appreciate it if you could help me with that. so this shouldn't be an issue, don't you think so? |
Strange... You are right! It should work. But when i try to start my app i get this output:
|
i guess this is the problem (after npm i ngx-mat-select-search):
|
So i guess the problem is So for Angular 6 Support we would need to update rxjs to 6.0.0... I wonder if that would break the support for older Angular versions... |
we could specify the dependency as follows:
but in your case, there should already be a rxjs version in the |
Yeah i already have the VSCode even recognizes every import when i open this module from the |
in https://stackblitz.com/github/Avejack/ngx-mat-select-search it seems to work with angular 6... |
@Avejack I can reproduce your errors with a new angular project with the following versions:
|
yeah... totally strange. |
There is another problem: |
I also tried re-building the package with angular cli 1.7.4 and ng-packagr 2.4.2 - with the same result. |
@Avejack the imports could finally be changed to be compatible with Angular 5.x.x and 6.x.x by changing
to
|
nice! |
Hey!
What do you think about adding Angular 6 Support?
I am not sure but i think it would not be possible to support older versions then... Maybe a ng6 branch? The Problem is that Angular 6 is using the RxJS v6 and there imports have changed. Also "takeUntil" now needs to be piped and stuff. I can make a PR for that but i don't know how you feel about the fact that this may lead to a breaking change in a way where it won't support older Angular versions anymore...
The text was updated successfully, but these errors were encountered: