[WIP] Explicit proxies

[trek]

Just a WIP for having more complex proxy behavior.

Proposed changes:

• renames api-stub generator to http-mock, which is maybe more accurate? :bikeshed:
• adds an http-proxy with example proxy: ember g proxy api 127.0.0.1:8000
• updates server directory to include mocks and proxies
• makes proxies happen last in mocks, middlewares, proxies ordering
• make proxies with with requests that need to be streams
• tests

Nice to have

• leaves --proxy behavior, but warn if used when explicit proxies are generated

[rwjblue]

Definitely 👍 on the idea, ping when its ready for detailed review...

[stefanpenner]

i think the first /* can be dropped /**/*.js should be sufficient

[trek]

@EndangeredMassa said that accidentally tried to load server/index.js itself?

[stefanpenner]

ah, yes it would.

[stefanpenner]

any ideas if proxy should occur before or after other middle ware and if so how would one accomplish this

[stefanpenner]

@trek let me know if I'm blocking you on this one

[trek]

@stefanpenner I can see problems with both proxy orderings: before and after. Should we just pick one and let it fly? I'd think letting new middleware break apps would be worse than letting proxies break middleware but both seem bad.

Do you have an example of what the middleware do? we've never used one.

[stefanpenner]

@trek can we make proxies just happen last? I suspect if someone overrides a route explicitly they understand and expect that functionality

[trek]

roger roger.

[stefanpenner]

@trek once you feel good about this, if you can add an integration test (so we can ensure the generator keeps generating something that actually proxies) that would be awesome.

Other then that i think this is good, once you think its good give it a good change-log entry and pull the switch.

[trek]

not a huge fan of files/server/index.js appearing in both blueprints. Is there some way to share?

[stefanpenner]

@jgwhite thoughts?

[jgwhite]

@stefanpenner @trek long-term, taking Thor as inspiration, my feeling is that blueprints should have a set of utility functions along the lines of:

• Blueprint#addFile(file, location)
• Blueprint#addPackageToProject(package, version)
• Blueprint#addRouteToRouter(route, options)
• Blueprint#installOtherBlueprint(name) (this would have to delegate to the host task for lookup paths)
• …

[trek]

test failures seem to be install/build based?

[bcardarella]

@trek AppVeyor builds are broken for now

[stefanpenner]

it looks like travis is also broken for the PR: https://travis-ci.org/stefanpenner/ember-cli/pull_requests

[EndangeredMassa]

Green travis-ci build, at least. https://travis-ci.org/stefanpenner/ember-cli/builds/31859850