naming issues

[PatrickHeneise]

Thanks Witold for the efforts and for putting the library into bower. I'm wondering why the file is called 'angular-http-auth' and the module 'http-auth-interceptor'? A more consistent naming would be convenient. Also the library should be directly in the folder, not in the subfolder /src, to stick to bower defaults.

[witoldsz]

Hi, I am sorry, but I did not put this project into bower. I am sorry, but I don't even know what the bowler is.

[PatrickHeneise]

Oh, the repository links straight here (I found the repo before from your blog).

Bower is to JavaScript like npm to node.js, a package manager which is heavily used by AngularJS folks for managing libraries. It's pretty cool and makes things easier (bower install angular-http-auth installs your library).

[PatrickHeneise]

https://github.com/Iristyle/bower-angularAuth

[drozzy]

+1 for this.

[Narretz]

+1 for Bower integration with consistent naming scheme "angular-http-auth-interceptor"

https://github.com/twitter/bower

Registering packages

To register a new package, there must be a valid manifest JSON in the current working directory, your package must be available at a Git endpoint (e.g., GitHub), and it should use semver Git tags. Then run:

bower register <my-package-name> <git-endpoint>

The Bower registry does not have authentication or user management. It's on a first come, first served basis. Think of it like a URL shortener. Now anyone can run bower install , and get your library installed.

There is no direct way to unregister a package yet. For now, you can request a package be unregistered.

[kailuowang]

+1

[witoldsz]

Sorry for late reply. Last few months were terrible, did not have time for this. I hope this will change in a week or two, so I could test drive the bower.

[witoldsz]

The module is officially in bower. It was there even before I merged the pull request. Now, I cannot change the name of the module or bower project name, this would break all the projects using this.