Commit Graph

14 Commits

Author SHA1 Message Date
Brendan Forster dc2f6ff001 first pass at cleaning up attributes (#2157) 2020-03-18 09:02:11 -03:00
Brendan Forster f96885654f add metadata to each client action (#2124) 2020-03-04 21:10:38 -04:00
Itai Bar-Haim 4e804f61a6 Prefer using nameof(x) over literal "x" (#1781)
* updated XML docs and added some missing bits.

* prefer nameof(x) over literal "x"
2018-03-07 20:43:10 +10:00
Andreia Gaita 9e958bf998 Make Repository Id a long, it's going to grow... 2016-09-15 02:15:11 +02:00
aedampir@gmail.com 44b0f4039d ID -> Id 2016-07-17 16:29:32 +07:00
aedampir@gmail.com 36c20079a7 removed <retuns> tags 2016-07-07 03:10:31 +07:00
Alexander Efremov b198b47254 cleared <returns> tags 2016-06-17 05:41:03 +07:00
Alexander Efremov 7bbbc7e74b added new overloads
modified XML docs a little bit
2016-06-12 14:27:23 +07:00
Mordechai Zuber 44304ca70b use string per recommended style 2015-12-16 21:23:36 +02:00
Micah b141703dbd Adds TreeClient.GetRecursive method.
Initially I implemented this as an optional parameter that would append "?recursive=1" to the end of the URI if an optional recursive boolean was supplied to the TreeClient.Get method.  Unfortunately, code analysis complained about that so I went with a set of new overloads instead.

Let me know if a different approach is preferred for adding optional query string parameters to API methods or if this is the preferred solution.  The problem with this solution is that it doesn't scale out well with multiple optional parameters.
2015-01-11 14:31:55 -08:00
Haacked c96b00650e Add comments to concrete types
We now have a build task that copies comments from interface to
implementation.
2013-12-11 14:22:39 -08:00
Peter MacNaughton 3b7488c4da API client constructors documented 2013-12-02 22:09:04 -07:00
Brendan Forster 06737995ed catch an obscure requirement when creating trees 2013-11-27 12:37:58 -08:00
pltaylor 59441ed030 Implement Observable Tree client and refactor names 2013-11-11 08:45:48 -05:00