Looks good to me. @peterflynn did you still have concerns about removing the deprecated method in this sprint? I didn't see any conflicts with the filesystem API changes.

Clarifying title. @rovenman in the future, please use a descriptive pull request title rather than just the bug number -- thanks!

@jasonsanjose No, it's fine as far as the filesystem API changes go. The API was only deprecated in sprint 32, which isn't too long ago (definitely less time than we usually wait before removing deprecated APIs). But because we're in the special case of making larger breaking API changes this sprint anyway, maybe it's ok this time.

Ok, now I'm more strongly sure it's ok. Of the three extensions I'm aware of that were using this API when it became deprecated, only one is still using it (angularui.angularjs) and it will be broken in Sprint 34 either way (unless updated) due to filesystem changes.

Done. Let's pile 'em up now. 🎢

@peterflynn Alright, didn’t know that, please excuse my ignorance.