Request tokens endpoint #3
Conversation
… for searching these endpoints
| } | ||
| } | ||
|
|
||
| public static void DrugSearch(Client client) |
There was a problem hiding this comment.
What are your thoughts on combining the drug-related examples into one class, and ditto for form ones? Then perhaps extracting each into their own files so that Program.cs just has the Main class in it?? I haven't done any .NET programming in awhile, but IIRC correctly that's a common practice.
There was a problem hiding this comment.
That would be a good idea. I was mainly using the CoverMyDotNet.Samples to make sure the client class was working correctly with the api. Ill make those changes though.
|
|
||
| namespace CoverMyDotNet.Requests | ||
| { | ||
| public class SearchForm : RestRequest |
There was a problem hiding this comment.
Is there a reason that we have one class per API method rather than one per API? Perhaps there is a technical reason imposed by RestSharp, or was this the desired usage?
There was a problem hiding this comment.
@twyfordr RestApi doesn't force you to do that, but I thought that it was the best way to go.
Endpoint that deals with creating and deleting tokens.