Http incorrect Verb generation #115

Activity

1. faniereynders commented on Sep 16, 2016

   

   faniereynders

   on Sep 16, 2016

   Member

   More actions

   Hi @CalinBunea the generation is using the API Explorer from within ASP.NET to determine the correct verb and is not per convention directly, however the route resolver in ASP.NET uses convention if the verb is not explicitly defined on the action.

   Can you provide me with a snippet of your controller?
2. CalinBunea commented on Sep 16, 2016

   

   CalinBunea

   on Sep 16, 2016

   Author

   More actions

   Well when I access my webservice /api/proxies for that specific method I have

   getPsPopularityDataForSearchPhrases: function(countryPrefix,searchPhrases,options) {
        var defaults = { fields: [] };
        var settings = $.extend({}, defaults, options || {});
        var url = "api/Munin/GetPsPopularityDataForSearchPhrases?countryPrefix=" + countryPrefix;
   
        if(settings.fields.length > 0) {
           url +=  url.indexOf("?") == -1 ? "?" : "&";
           url += "fields=" + settings.fields.join();
        }
   
       return invoke.call(this, url, "post", 
                   {
                           countryPrefix: countryPrefix,
                       }
                           , searchPhrases);
           },
   

   the method in controller:
   [HttpPost]
   public List GetPsPopularityDataForSearchPhrases(string countryPrefix,List searchPhrases)
   {
   ......
   }

   and the generated client proxy
   public virtual List GetPsPopularityDataForSearchPhrases(String countryPrefix,List searchPhrases)
   {
   var result = Task.Run(() => GetPsPopularityDataForSearchPhrasesAsyncMsg(countryPrefix, searchPhrases)).Result;

           EnsureSuccess(result);
   
           return result.Content.ReadAsAsync<List<PsPopularityData>>().Result;
                   }
   
3. CalinBunea commented on Sep 16, 2016

   

   CalinBunea

   on Sep 16, 2016

   Author

   More actions

   Small update, I have renamed the method (to not include "get" in name) but still the verb generated is GET...
4. CalinBunea commented on Sep 16, 2016

   

   CalinBunea

   on Sep 16, 2016

   Author

   More actions

   Another update: I think this issue was caused by a method overload. One of the methods didn't had [HttpPost] and probably this is why the second method (overloaded) which has [HttpPost] was still generated to use verb GET.