[x ] bug report => Search github for a similar issue or PR before submitting
Current behavior
After upgrading primeng from 4.1.3 to 4.2.0-rc.1, I get this build error in my Angular.io project:
ERROR in ng:.../web/ewp/objs/node_modules/primeng/components/dropdown/dropdown.d.ts.Dropdown.html (6,13): Type 'string' is not assignable to type 'boolean'.
Expected behavior
Should build without errors
Please tell us about your environment:
Linux
Angular.io with angular-cli
Here is my package.json file:
{
"name": "d3",
"version": "0.0.0",
"license": "MIT",
"scripts": {
"start": "ng serve",
"lint": "tslint \"src/**/*.ts\"",
"test": "ng test",
"pree2e": "webdriver-manager update",
"e2e": "protractor"
},
"private": true,
"//": "#################################################################################################################################",
"//": "Comments go here",
"//": "#################################################################################################################################",
"dependencies": {
"@angular/cli": "1.3.2",
"@angular/common": "4.3.6",
"@angular/animations": "4.3.6",
"@angular/compiler": "4.3.6",
"@angular/compiler-cli":"4.3.6",
"@angular/core": "4.3.6",
"@angular/forms": "4.3.6",
"@angular/http": "4.3.6",
"@angular/platform-browser": "4.3.6",
"@angular/platform-browser-dynamic": "4.3.6",
"@angular/router": "4.3.6",
"@angular/material": "2.0.0-beta.8",
"@angular/cdk": "2.0.0-beta.8",
"@types/hammerjs": "2.0.35",
"hammerjs": "2.0.8",
"core-js": "2.5.0",
"primeng": "4.2.0-rc.1",
"rxjs": "5.4.3",
"ts-helpers": "1.1.2",
"zone.js": "0.8.17"
},
"devDependencies": {
"@types/jasmine": "2.5.54",
"@types/node": "8.0.25",
"@types/chrome": "0.0.48",
"angular2-template-loader": "0.6.2",
"codelyzer": "3.1.2",
"jasmine-core": "2.8.0",
"jasmine-spec-reporter": "4.2.1",
"karma": "1.7.0",
"karma-chrome-launcher": "2.2.0",
"karma-cli": "1.0.1",
"karma-jasmine": "1.1.0",
"karma-remap-istanbul": "0.6.0",
"protractor": "5.1.2",
"ts-node": "3.3.0",
"tslint": "5.7.0",
"typescript": "2.2",
"webdriver-manager": "12.0.6"
}
}
Angular version: 2.0.X
4.3.6
PrimeNG version: 2.0.X
4.2.0-rc.1
I'm pretty sure this commit fixed it, but didn't reference this issue
same issue
same issue
commit didn't fix https://github.com/primefaces/primeng/issues/3780
Am facing this issue in "primeng": "4.2.0-rc.1",
same issue in "primeng": "4.2.0-rc.1",
Confirmed, this issue exists in aot build.
Same issue on aot after update primeng to v4.2.0-rc1
I am having the same issue as well :-) - What would be the latest primeng release where AOT works fine?
Same issue here too, after update primeng to 4.2.0-rc.1
same issue
Commenting that you have the same issue really only clogs up the thread. Unless you have something constructive to say or a question, just thumbs up the issue.
Is there any temp solution to build without errors?
@jesusce21 revert to 4.1.3 ?
Same problem here. Reverting to 4.1.
I just reverted to 4.1.3 and it built successfully.
Same
same issue
+1
@cagataycivici - It looks like the fix for this has been in place for over a week. Any plans for a release in the near future so we can build again?
THIS ISSUE IS ALSO AFFECTING ME!!!
Any plans for releasing v4.2.0-rc2, fixing this issue?
I'm having the same issue
+1
same problem
Same issue
same here
Same here +1.
Thanks.
+1
+1 in 4.2.0-rc.1,when run ‘--prod’。
but 4.1.3,it works good。
+1
I fixed replacing *ngIf=\"!editable&&label\" to *ngIf=\"!editable&&!!label\"
Thanks @eminoda downgrading to 4.1.3 worked for me too
@saskyagurgel can you post your file or tell us the file location to put this code? By the way, if I downgrade to 4.1.3 I can't use the MessageService class. Please help me.
@adityals i'm changed the file ...\node_modules\primeng\components\dropdown\dropdown.metadata.json
replacing *ngIf="!editable&&label" to *ngIf="!editable&&!!label"
+1
Fixed for 4.2.0 already.
4.2.0 is released now, please try with this one.
No build error now (with 4.2.0)! Thanks!
Most helpful comment
4.2.0 is released now, please try with this one.