Topic: Error after Update to Angular 6
Hey,we upgrade our devenv and project from Angular 5.2 to Angular 6 as its described at the http://update.angular.io page.But now we get the following error when we try to start \"ng build\".
ERROR in node_modules/ng-mdb-pro/free/dropdown/dropdown.directive.ts(158,9):
error TS2339: Property \'filter\' does not exist on type \'EventEmitter<boolean>\'.
node_modules/ng-mdb-pro/pro/autocomplete/directives/input.directive.ts(132,33):
error TS2339: Property \'timer\' does not exist on type \'typeof Observable\'.
node_modules/ng-mdb-pro/pro/autocomplete/directives/list-context.directive.ts(121,37):
error TS2339: Property \'timer\' does not exist on type \'typeof Observable\'.
node_modules/ng-mdb-pro/pro/autocomplete/directives/list-context.directive.ts(133,34):
error TS2339: Property \'timer\' does not exist on type \'typeof Observable\'.
node_modules/ng-mdb-pro/pro/autocomplete/services/remote-data.service.ts(71,8):
error TS2339: Property \'map\' does not exist on type \'Observable<Response>\'.
We also generate a new Angular project based on your \"5 minute starting tutorial\" by getting the MDB Sources from Git. There will be the same error.
Do you have any idea how we can fix this problem?
Best regards
Robert
need help, i also got the same error when i update to angular 6.. i already installed rxjs-compat@^6.0.0-rc.1 but it doesn't solve my problem.. thank you in advance :) ERROR in node_modules/angular-bootstrap-md/dropdown/dropdown.directive.ts(158,9): error TS2339: Property 'filter' does not exist on type 'EventEmitter<boolean>'.
Damian Gemza staff commented 6 years ago
Dear Paolo, Please open node_modules/angular-bootstrap-md/dropdown/dropdown.directive.ts file and search for block which starts with this._subscription.push(this._state – line 158, and change this whole block of code with code from below: this._subscriptions.push(this._state .isDisabledChange // .filter((value: boolean) => value === true) .subscribe((element) => { if (element === true) { this.hide(); } })); Best Regards, Damian
rxjs-compat.--Damian Gemza staff commented 6 years ago
For now, rxjs-compat is necessary for our library, but with next release, it won't be. Best Regards, DamianFREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Answered
- ForumUser: Pro
- Premium support: No
- Technology: MDB Angular
- MDB Version: -
- Device: -
- Browser: -
- OS: -
- Provided sample code: Yes
- Provided link: No
Alellouche pro commented 6 years ago
You need to add rxjs-compat module.Damian Gemza staff commented 6 years ago
As Alellouche said, you have to type npm install rxjs-compat@^6.0.0-rc.1 --save. We will fix this problem with next release of MDB Angular. Best Regards, DamianArsenii pro commented 6 years ago
Dear Damian, Can you please provide some approximation of when it will happen? I also downloaded the last version of library 6.0.2 and not sure it’s safe to use it because I’ve found git repo there with uncommited changes to the project. Best Regards, ArseniiDamian Gemza staff commented 6 years ago
Dear Arsenii, 6.1.0 Release will be live on 21th May (next Monday). On which repo did you found some uncommitted changes? I would like to check it. I'm waiting to hear something from you. Best Regards, DamianArsenii pro commented 6 years ago
Dear Damian, Thank you for the date sharing. So 6.1.0 will be without legacy dependencies, right? I just loaded mdb as usual from: Profile -> Account -> Orders & Invoices -> button MDB_ANGULAR_PRO_6.0.2.ZIP. Resulted zip had .git folder inside and uncommited changes. I've tried it yesterday and today with the same result. Best Regards, ArseniiDamian Gemza staff commented 6 years ago
Yeah, that's natural. Zip package is not a repository, so we're not committing and pushing those changes to some repo. You can ignore it, because those uncommitted changes won't produce you the problems.Arsenii pro commented 6 years ago
Don't you think it's not good? As a user I naturally expect to see no git or git in some correct state when I get initial project to start work with. Instead as a windows user with tortoise git installed I see a lot of red folders which is naturally not the good point to start. But even if I was other system user I could decide that git is properly initialized, make some initial changes to the project, commit and then see all of those unexpected things in commit. The third thing that by these changes I see what you are doing with the project and may be you would like that information to be kept private. :)Damian Gemza staff commented 6 years ago
Thanks for your suggestion. We'll think about it with releasing new version of zip package.