body handleAs String and not manage JSON Object

[jmorille]

The core-ajax accept only string and not Json Object in body attribute.

The core-ajax should detect in body in order to apply the JSON.stringify(bodyObject) when is needed

Exemple

<polymer-element name="post-test">
  <template>
    <core-ajax id="ajax"
      url="/api/post"
      method="POST"
      handleAs="json"
      body="{{bodyObject}}">
    </core-ajax>
  </template>
  <script>
  Polymer({
   bodyObject : {
                fron : 0,
                size: 10,
                body: {
                    query: {
                        match_all :{}
                    }
                }
            } ,
       postHandler: function() { 
            this.$.ajax.go();
        }

  });
  </script>
</polymer-element>

It was post as

Request Payload
[object Object]

instead of

Request Payload
{"from":0,"size":10,"_source":["categorie","solution"],"body":{"query":{"match_all":{}},"aggs":{"statut":{"terms":{"order":{"_count":"desc"},"field":"statut"}}}}}
Response Headersview source

[mnowakowski]

It seems to me that my problem is related to the above. I get the following error on the console.log: "Unexpected end of input". I have method POST with 'body' attribute defined like in doc example:

body='{"name":"{{name}}"}'

After changed to this one:

body="{'name':'{{name}}'}"

the problem disappeared!! :)

[Will-in-BC]

I am not sure what the design point should be. It would be nice if core-ajax could be made to behave the same way as $.post from JQuery (see: http://api.jquery.com/jquery.post/) $.post will accpect any plain object (see link for definition) and pass as a query string.

With the version of core-ajax (0.4.2) I am using params will parse a single level object correctly into a query string but fails on a nested object. Using body causes the entire unparsed json string to be passed. Neither of the these matches the JQuery functionality. See:

http://stackoverflow.com/questions/26720573/passing-nested-objects-in-polymer-core-ajax

The reason for compatibility is simple. If you want to gradually replace a JQuery front end with a Polymer one it would be nice to be able to keep the backend the same.

Perhaps core-ajax needs an attribute to force an object to be passed as a query string.

[jmorille]

That a good idear to add an attribute like jquery.post ( ex: bodyType="json") to help the parsing the body. To keep the same Api of JQuery could effectively help to migration from JQuery.

In fact, It was testing Polymer with creating an CRUD application and the use of core-ajax is an a little bit painful to wrap core-ajax in another polymer element just to do that.

The current solution is to use an another boilerplate property (datastring)

<polymer-element name="tt-ajax-save" hidden attributes="index data response entityid">
    <template>
       <core-ajax id="service" url="/s/entityx/{{entityid}}" handleAs="json" contentType="application/json"
                   body="{{datastring}}" method="POST"  response="{{response}}" >
        </core-ajax>
    </template>
    <script> 
        Polymer('tt-ajax-save', {
            datastring : '',
            saveEntity: function () {
                 this.datastring =  JSON.stringify(this.options);
                this.$.service.go();
            },
          ...

instead of what you suggest that permit to use directly the core-ajax for persist entity

   <core-ajax id="service" url="/s/entityx/{{entityid}}" handleAs="json" contentType="application/json"
                   body="{{data}}"  bodyType="json"
                   method="POST"  response="{{response}}" >
    </core-ajax>

In fact in practice, we manipulate more the json object that the string representation.

Do you think that be possible to include this new feature in the next release ? (it does not seem to be risky ?)

cf pull Request : #41

[ianbibby]

+1
Encountered this when trying to make a POST to a Rails app using strong parameters, where nested parameters are common.