In ExtJS 4 (or possibly earlier) I believe it was possible (or at least tolerated) to delare the "requires" element as either a string (if a single class was required) or an array for multiple required classes.
With the new ExtJS plugin installed, opening a class which has the requires declaration formatted like this:
will cause the auto-populate of the requires array to continually add
to the top of the class until the string version is removed.
Removing the (old and probably not correct) string-based requires declaration stops the looping.
Possibly a bug, certainly not a high priority but might be a gotcha for people bring old code into projects with the new plugin active.
With the new ExtJS plugin installed, opening a class which has the requires declaration formatted like this:
Code:
requires: 'myApp.model.MyThingy',will cause the auto-populate of the requires array to continually add
Code:
requires: ['myApp.model.MyThingy',]to the top of the class until the string version is removed.
Removing the (old and probably not correct) string-based requires declaration stops the looping.
Possibly a bug, certainly not a high priority but might be a gotcha for people bring old code into projects with the new plugin active.
"Manage requires array" loops if requires element exists as a string (not array)
Aucun commentaire:
Enregistrer un commentaire