Jathan McCollum

I've started reviewing the reality of this and came across "DRF serializer extensions". It has some really cool stuff built that is more highly optimized than the default DRF "depth"...

So far in my initial research my favorite is "DRF serializer extensions", but here are some other's I've been tracking for reference. I'm posting these here because I'm sick of...

This particular pattern for deeply nesting serialization is also worth looking at: https://machinalis.com/blog/nested-resources-with-django/

Thanks for the request! Unfortunately, this doesn't strike me as a compelling use-case for a top-level resource type. Internally at Dropbox, for example, we are using `vlan` as a Network...

That's good feedback! I'd like to understand this better in that case.

@jwbensley This is really helpful and will be useful as we attempt to implement this object. Thank you for providing this input!

We've talked about that before using the "Location" concept. Is this kind of what you're thinking? See: https://github.com/dropbox/nsot/issues/186

To mirror what we discussed on Slack: > I really want to be able to have dashboarding done by existing attributes, since attributes are all user-defined, I think this would...

The first paragraph could be satisfied pretty easily using existing API filtering by adding nested related fields as filter fields (e.g. `endpoint_a__device_hostname` or `endpoint_z__device_hostname`), but man are those long and...

Ok, deep linking this to the Trigger issue (https://github.com/trigger/trigger/issues/231) adds the missing context to the hooks suggestion.