[Doc] Multi Provider dependency order

[trollkotze]

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Feature request
[x] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Questions like this are unanswered. Nobody knows, or at least it seems so to me, and I cannot find relevant documentation.

Expected behavior

Would be good to find straightforward information about this in the documentation.

Minimal reproduction of the problem with instructions

My problem is as follows:
I want to use a custom AuthInterceptor for use with HttpClientModule, but also need the JsonpInterceptor from HttpClientJsonpModule.

I am doing like so in my AppModule:

    imports: [
        ...,
        HttpClientJsonpModule // this provides JsonpInterceptor to the HTTP_INTERCEPTORS token
        ...
    ],
    providers: [
        ...,
        { provide: HTTP_INTERCEPTORS, useClass: AuthInterceptorService, multi: true },
        ...,
    ],

But order of injection is important here!
I don't know how to control the order of injection for the HTTP_INTERCEPTORS multi-provider.
In my scenario it seems to happen so that the JsonpInterceptor provided by HttpClientJsonpModule is added first to the HTTP_INTERCEPTORS, which means, it will be called first in the chain of interceptors. I want exactly the opposite, because the JsonpInterceptor will not call next() to let any other interceptors run through if it finds a jsonp request. But I don't know a way to change the order.

What is the motivation / use case for changing the behavior?

Inform developers better so that they don't have to waste so much time searching and reading the angular core code to find andswers. Because time is valuable.

Environment

Angular version: 5.2.9

Browser:
[x] not a browser issue
 
For Tooling issues:
- Node version: v9.2.0, but shouldn't matter
- Platform:  Linux, but really shouldn't matter

[angular-robot]

Just a heads up that we kicked off a community voting process for your feature request. There are 20 days until the voting process ends.

Find more details about Angular's feature request process in our documentation.

[angular-robot]

Thank you for submitting your feature request! Looks like during the polling process it didn't collect a sufficient number of votes to move to the next stage.

We want to keep Angular rich and ergonomic and at the same time be mindful about its scope and learning journey. If you think your request could live outside Angular's scope, we'd encourage you to collaborate with the community on publishing it as an open source package.

You can find more details about the feature request process in our documentation.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}