Ultima NG 1.0.2 issue

[treydrake]

Folks,

Post install (ultima-ng-1.0.2) I immediately get the below error. Poked around and didn't see anything obvious to fix other than tacking on CUSTOM_ELEMENTS_SCHEMA to the app.module (saw a note on this via StackOverflow that was only a few hours old). Doing so didn't change a thing. Suggestions?

polyfills.js:6750 Unhandled Promise rejection: Template parse errors:
Can't bind to 'numberOfMonths' since it isn't a known property of 'p-calendar'.
1. If 'p-calendar' is an Angular component and it has 'numberOfMonths' input, then verify that it is part of this module.
2. If 'p-calendar' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the '@NgModule.schema' of this component to suppress this message.
(" </div>
<div class="ui-g-12">
<p-calendar id="multiple" [ERROR ->][numberOfMonths]="3" placeholder="Multiple"></p-calendar>
</div>
<div"): FormsDemo@83:46
...

[mert.sincan]

Which primeNg version are you using with Ultima?

[treydrake]

primeng@1.0.0-beta.20

Thanks

[mert.sincan]

We added native calendar to primeNg beta.19+. Please see; http://blog.primefaces.org/?p=4149
Therefore, our native calendar component has not numberOfMonths attribute. please try it after removing this attribute. Also, please see attribute list of native calendar;
http://www.primefaces.org/primeng/#/calendar

[treydrake]

Duh, should have caught on to that in the logs - works after commenting out the offending attribute. Suggest adding this nugget to the Ultima NG release notes. Thanks.

[mert.sincan]

Thanks for the update!

[bigpanda]

I have encountered the same thing.
Could you please remove this property

Code: Select all

numberOfMonths

on the next release?
Thanks.