Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
add an /applications/details endpoint which corrects problems with /fetch #967
and adds some new features:
noticed that fetch actually recurses through all children entities which was never the intention and is wasteful at scale. also for usability it would be nice to include tags and all/regex sensors and config values. this adds support for that.
i've deprecated the existing
to make this easier i've promoted
I'll add tests and push all changes addressed except depth.
On maxDepth, it's a not uncommon pattern that <0 is infinite, and 0 could to me logically mean either no detail at level 0, or yes detail at level 0 but 0 additional levels. I've gone with the former semantics as strictly more useful (in terms of functionality). The fact that the default is 1 and this is explained I think is sufficient.
Agree both are a little subtle but there is not an elegant way I can see to make it clearer; it involves additional fields with some redundancy.
If you feel strongly happy to go with an alternate API that preserves functionality -- please suggest -- however this as is my preferred.