Pods Support + Classic/Pods Hybrid Support

[NullVoxPopuli]

pods structure can now be migrated from.

This PR just adds to the existing code. I think a future PR should be a refactor. Lots of things need to be extracted to methods for easier inheritance.

[rwjblue]

This is looking really good! Thank you so much for working on it!

@mixonic / @andyhot - Mind reviewing also?

[Subtletree]

Looks like this currently wouldn't work for apps with no podModulePrefix or for any where podModulePrefix !== 'pods'. Is that right?

Have a decent sized app with mostly pods but some classic. Keen to help with testing if possible

[andyhot]

@rwjblue taking a look this weekend @Subtletree unless there's a regression (which judging from the passing tests there shouldn't) classic structure just works. If there's indeed a requirement for podModulePrefix to be 'pods', we'll fix that - i too have apps where that's not the case :)

[NullVoxPopuli]

how do you get access to the podModulePrefix?

[NullVoxPopuli]

so, here is my plan: I'm going to assume config/environment.js, and require/import that file, and get the podModulePrefix that way.

Is there any scenario where that wouldn't work?

[NullVoxPopuli]

Work on namespaceless pods: https://github.com/NullVoxPopuli/ember-module-migrator/pull/1

[NullVoxPopuli]

namespacelessness is gettitng there. I have a path to doing it, just need to work out some kinks

[NullVoxPopuli]

Node 4 had a syntax error????? SyntaxError: Unexpected token {

[rwjblue]

Probably destructuring

[NullVoxPopuli]

The failing tests are 'just' timeouts. :-\

[NullVoxPopuli]

@rwjblue squashed!

[NullVoxPopuli]

eslint check on node 7 timed out

[rwjblue]

restarted that one, but we should drop Node 7 in a followup PR