It looks like commit 7b40ba8 removed the last reference to CollectionUtils from Brackets core. This means that any extensions using the module will fail to load since the brackets.getModule() call will fail.
(Edit: we restored the reference for now (2nd bullet below), and this bug is now just tracking the remaining work to fully remove it later once extensions have had more time to migrate)
CollectionUtils contains only deprecated methods, so this needs to happen sooner or later anyway. But we should cleanly either:
Assigning to Sprint 36 since we should make a decision about this before the sprint goes out the door
For now we're going to keep the module available, but I'll go file bugs against any extensions still using it so we can remove it in the near future (Sprint 37?).
@peterflynn - this was assigned to Sprint 37, but it seems like we have to do a bit of work in Sprint 36 (adding the reference in brackets.js) in order to keep it working, right? It doesn't look like that got done yet, so putting this back in Sprint 36 so we remember to do it.
@peterflynn Should this Milestone now be moved to Sprint 37?
@redmunds You mean turn it into a bug tracking the final removal of the API? That seems fair, though I don't know if it needs any milestone in particular in that case. I'll make the adjustment.
Removed Sprint 36 Milestone.
Changed title (was: "CollectionUtils is no longer usable by extensions") and reduced priority -- changing this into an issue tracking the eventual removal of the module for good.
#8960 removed CollectionUtils.