jQuery UI Widgets › Forums › General Discussions › Angular › error on DateTimePicker
Tagged: Angular2
This topic contains 6 replies, has 2 voices, and was last updated by Matthias 9 years, 3 months ago.
-
Authorerror on DateTimePicker Posts
-
In the DateTimePicker there is a closing curly brace missing in line 131.
The error is in version 4.4.0 on your website and the 4.4.0 get by bower.We see no error in the browser’s console in the demos: http://www.jqwidgets.com/angular2/angular2-datetimeinput/angular-datetimeinput-defaultfunctionality.htm?light
I tried your link and the files it uses.
The Demo works and the file http://www.jqwidgets.com/angular2/jqwidgets-ts/angular_jqxdatetimeinput.ts!transpiled looks right. But the http://www.jqwidgets.com/angular2/jqwidgets-ts/angular_jqxdatetimeinput.ts seems to be incorrect. The curly brace from the setTimeout() isn’t closed. It doesn’t seem like the …ts!transpiled is transpiled from the ts, because in the …ts!transpiled the curly brace is closed.Hi Matthias,
Well, we don’t do the transpiling. A tool does and it is transpiled exactly from that .ts file as we have no other file uploaded.
Best Regards,
Peter StoevjQWidgets Team
http://www.jqwidgets.comI copied the part of the code
In the http://www.jqwidgets.com/angular2/jqwidgets-ts/angular_jqxdatetimeinput.ts (129) there is written:setTimeout(() => { options.value !== undefined ? this.host.jqxDateTimeInput('val', options.value) : this.host.jqxDateTimeInput('val', new Date()); , 1);In the http://www.jqwidgets.com/angular2/jqwidgets-ts/angular_jqxdatetimeinput.ts!transpiled (100) there is written:
setTimeout(function () { options.value !== undefined ? _this.host.jqxDateTimeInput('val', options.value) : _this.host.jqxDateTimeInput('val', new Date()); }, 1);The Problem is the curly brace before the “, 1”. Either the code is not transpiled from the ts or the tool ist so smart to repair such mistakes by its own.
Hi Matthias,
Obviously, it is smart enough 🙂
Best Regards,
Peter StoevjQWidgets Team
http://www.jqwidgets.comProblem is fixed in 4.5.0
-
AuthorPosts
You must be logged in to reply to this topic.