Timeline for WebAPI Client Proxy
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 27, 2015 at 16:17 | comment | added | moarboilerplate | @ThomasEyde Coming back to this, I realized you could fix both the dependency issues and your concerns about the design by inverting the dependencies. Make your Users an instance class that takes the MyProxy instance in the constructor, and then delegate your calls to the proxy. Wire the injection up using a container. Now you can mock/stub out your proxy object and behavior and isolate it in testing, you have no access modifier concerns, and you have the added benefit of being able to mock out your Users object to test consuming code since it's no longer static. Hey, you have a repository! | |
| Oct 5, 2015 at 12:57 | comment | added | Thomas Eyde | Using a code generator is not that fun when it generates incompatible code. Then you have to manually hunt down all the compiler errors and fix them. That's easy, but boring, when there's a one-to-one mismatch, like a rename. Not so fun when there are more complex changes. | |
| Jul 24, 2015 at 21:36 | history | answered | moarboilerplate | CC BY-SA 3.0 |