Pablo Largo Mohedano

Hi @veewee, sorry for the late response! It is true that `converted()` would be a better candidate for the case I presented. However, the `coerce()` behavior looks too forgiving for...

I'm looking forward to this, I think this is going to be mandatory for a lot of transactions.

@bmeynell I'm using the latest release, and that PR seems integrated. I've just found another StackOverflow, but it doesn't work too. https://stackoverflow.com/questions/14534234/deserializing-doctrine-references-with-jmsserializer The error right now would be something like...

@goetas I will try to test carefully a new pair of entities on a different environment tonight at home, I'm struggling at work with urgent things :( Edit: That's what...

I agree with all the points! I would add a couple of ideas: - Define better some terms like `transactionId` and `referenceId`, used ambiguously by different drivers, making them incompatible....

I don't know how far I'll reach, but I'm going to start a little effort to propose a new major version: https://github.com/devnix-labs/omnipay-common/tree/add-static-analysis I will consider your original ideas, but I...

The ambiguity of the price attribute is stopping me from implementing this. If there is any plan to add a `Money` parameter, I would be more than happy to help.

What concerns me is that there is not any kind of typehint about passing an int or a float. For example, I would expect passing `100` to send €1 to...

+1 to this. I don't get at all the difference between authorizing and charging, and when I should call `authorize` or `purchase` methods.

What does the log output? The best thing would be to get the uid automatically from the host via docker-compose.yml, and add to the dockerfile as a build parameter.