Brian Moseley

I'd want to initialize the client before the component using Stamps is ready for service in order to avoid race conditions. so for example, at component start up time, it...

it already exists :) https://github.com/mattsears/stamps/blob/master/lib/stamps/api.rb#L12

oh, just basically declaring a `savon` attribute in Stamps::API and moving that block you indicated earlier in the discussion into `Stamps::API.initialize`. I don't have time to work up a patch...

:+1: I've got similar behavior in an extension I've written (except mine handles params of type object as well by creating rails-style bracket names, eg `` for a param `foo`...

using `attr` instead of `data` is probably a simple mistake. and his use case probably requires `data('params')` to be set programmatically with an object. if @phillipp doesn't get around to...

> We could possible add some sort of default styling to complete the polyfill :+1: to that. we've had instances of developers going down rabbit holes trying to figure out...

Interesting idea. I've had the same problem but never came up with a solution.

this approach assumes that the response data is exactly the html string you want to stuff inside the target element. but what if the response data includes multiple items that...

I actually like the original patch's approach: ``` if (dataType == 'html' && target) { $(target).html(data); } ``` that's less ambiguous. if the server sends back raw html it probably...

not a terrible workaround. along those lines, a small change to how `url` is calculated in `handleMethod` would allow that method to be used for buttons as well.