I had one of this AARGH! moments today again (especially after I found the reason):
It took me way too long until I realized that the problem was the fact that the YUIParser disliked the fact that my package name used the name of a "Future Reserved Keyword" that was defined in ECMAscript 3.1 (it's not even there anymore in 5.1 or the v6 draft).
[5.0.2] Bug: Can't handle package names that have a reserved JS keyword like abstract
It's not uncommon for me to use a package name like "App.view.abstract" to declare abstract classes.
This worked flawlessly with SenchaCMD 5.0.0.
Now as I tried to build my app with Sencha CMD5.0.2 I was flabbergasted by the error message it suddenly produced when running sencha app build
[ERR] C2009: YUI Parse Error (missing name after . operator => if (!App.view.abstract) App.view.abstract = {};) -- unknown-file:17:22[ERR] C2009: YUI Parse Error (missing name after . operator => (Ext.cmd.derive('App.view.abstract.SingleRecordViewModel', Ext.app.ViewModel, {data: {rec: null}}, 0, 0, 0, 0, ["viewmodel.singlerecord"], 0, [App.view.abstract, 'SingleRecordViewModel'], 0));) -- unknown-file:75831:159
It took me way too long until I realized that the problem was the fact that the YUIParser disliked the fact that my package name used the name of a "Future Reserved Keyword" that was defined in ECMAscript 3.1 (it's not even there anymore in 5.1 or the v6 draft).
So there is no sane reason for this limitation, especially at this date (and there probably never was).
Please get this fixed!
(I'm aware that this might be related to the thirdparty software YUICompressor)
[5.0.2] Bug: Can't handle package names that have a reserved JS keyword like abstract
Aucun commentaire:
Enregistrer un commentaire