Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

In the docs, why is $injector categorized as 'service', but $provide as 'object'? #7917

Closed
thorn0 opened this issue Jun 20, 2014 · 1 comment
Closed

In the docs, why is $injector categorized as 'service', but $provide as 'object'? #7917

thorn0 opened this issue Jun 20, 2014 · 1 comment

Comments

@thorn0
Copy link
Contributor

thorn0 commented Jun 20, 2014

What is the logic behind this?
image
@thorn0 thorn0 changed the title In the docs, why is $injector categorized as a service and $provide as an object? In the docs, why is $injector categorized as a 'service' and $provide as an 'object'? Jun 20, 2014
@thorn0 thorn0 changed the title In the docs, why is $injector categorized as a 'service' and $provide as an 'object'? In the docs, why is $injector categorized as 'service', but $provide as 'object'? Jun 20, 2014
@petebacondarwin
Copy link
Contributor

$provide is not a "real" service, it is a kind of pseudo service, so in the code it is tagged as a global object. This is probably a mistake :-)

petebacondarwin added a commit that referenced this issue Jun 20, 2014
@petebacondarwin
docs($provide): it is a service not an object
ea653e4 
Closes #7917
ckknight pushed a commit to ckknight/angular.js that referenced this issue Jul 16, 2014
@petebacondarwin
docs($provide): it is a service not an object
b11f3aa 
Closes angular#7917
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@petebacondarwin @thorn0