> Place your test files next to the implementation.
ok.
> A resource always should be plural in the URL. Keeping verbs out of your resource URLs.
What does it have to do with Javascript projects?
> Avoid js alerts in production
alert is a DOM API, it doesn't have anything to do with Javascript.
-
Barely anybody pointed out the fact that this "guide" mixes up things that have nothing to do with each others.
How is file organisation related to how one name "subresources" in a rest API or browser alerts ? it isn't.
This isn't a serious document. It was hastly put together with no real considerations whatsoever and named "best practices" without any sources or links to give weight to these opinions.
Finally, as I said multiple times, coding style guides, "best practices" that cannot be validated automatically on a CI server are worthless and a waste of time in an business environment.
ok.
> A resource always should be plural in the URL. Keeping verbs out of your resource URLs.
What does it have to do with Javascript projects?
> Avoid js alerts in production
alert is a DOM API, it doesn't have anything to do with Javascript.
-
Barely anybody pointed out the fact that this "guide" mixes up things that have nothing to do with each others.
How is file organisation related to how one name "subresources" in a rest API or browser alerts ? it isn't.
This isn't a serious document. It was hastly put together with no real considerations whatsoever and named "best practices" without any sources or links to give weight to these opinions.
Finally, as I said multiple times, coding style guides, "best practices" that cannot be validated automatically on a CI server are worthless and a waste of time in an business environment.