gianarb/awesome-angularjs

Reformat to Contribution Standards

jimbuck opened this issue · 5 comments

jimbuck commented

Currently this list is a little wild, various versions of "Angular", "AngularJS", "angular.js", etc, as well as many lines without endings.

The basic clean up items are as follows:

  • Check and update all links.
  • Change all variations of angular's title to one version.
  • Add "." to the end of each description.

Regarding the name of angular in the list, we should adjust to make them all the same. Here are the options, please let me know which is the appropriate style.

  • Angular
  • AngularJS
  • Angular.js
  • angular
  • angularjs
  • angular.js

I will have a pull request coming shortly for the basic formatting, and once I hear back from @gianarb and others about what to call angular I will wrap it all up.

gianarb commented

Hello @JimmyBoh thanks for your feedback but the "name of angular" in my opinion is not a big problem because the role is very clear

<ownerRepo>/<repoName>

:) Why is this a problem?

jimbuck commented

Hey @gianarb I like consistency =]. If you don't think it needs it then I'll leave them as is.

gianarb commented

@JimmyBoh thanks but in my opinion this problem of "consistency" not exist...

The nomenclature is consistent with <ownerRepo>/<repoName> :)

jimbuck commented

Oh, no that is fine, I mean all the different names for AngularJS. For example, from the "Directives" section (bolded for emphasis):

As you can see, there is no standard name being used, everything is different case, with or without "JS", etc.

In my opinion, making "AngularJS" the standard spelling is the best option, since that is how it is spelled/formatted on angularjs.org.

This is how it would look after the update (ignore the bold):

jimbuck commented

@gianarb Any thoughts after looking at my example above?