Nick Acker

Nested resources more than one level deep are an anti-pattern, and should be avoided. A route like `POST /student/:studentId/course/:courseId/semester/:semesterId/subject` is a superfluous mess that is functionally identical to `POST /semester/:semesterId/subject`....

@sharathm Eh... I think that's a bit too simplistic a view of what a RESTful API is for me to say that that is correct. @breandr > those mostly look...

I think you'll run into a problem with assuming that you can expect dis/associating routes on every resource is that not every resource's association can be interacted with in that...

> If this is a one-to-many (a school has many courses) and you `DELETE > /school/:schoolId/course/:id`, this would simply delete the course record > (although I'd prefer to just have...

I believe it's more RESTful as it's targeting an actual resource (at least in the view of the client). I think the example is a bit poor and that might...

Done, thank you for taking the time to review & merge!

Also, added some docs updates that will also close #24

@GPrimola I've implemented this along with a few other changes in a fork here: https://github.com/theblitzapp/prometheus-ecto/tree/idle-and-repo-labels Check the PR linked above to see what else is changed; there are some breaking...

Generally, when I run into the need for this, I am trying to select, say, a variable name. But the variable name might be a pretty common word, or perhaps...

Yeah, I'm not a vintage man (yet?). Though there are a few less common occurrences that it could come in handy in but basically it comes down to any time...