Olivier Bellone

Thanks for the report @J-Priebe. This is expected behavior, but I agree we should do a better job of documenting it. Going to leave this open for now and we'll...

This is a bit tricky. We're trying to move away from the "update properties then call `save()`" approach, precisely because it conflates resource attributes and request parameters in a confusing...

My hope is that once we move to an autogenerated world, we would document update parameters in the PHPDoc of the `update()` method for each resource (we would no longer...

Tagging this as `future` as I don't want to rush into anything here. We're currently in the process of deploying new tooling to generate the resources and methods in our...

@virgofx The project is still in a very early phase so I don't have much concrete information to share yet, but yes, the idea is that we would use the...

Hi @adriaanvanrossum, thanks for the suggestion! This is an interesting idea. @rattrayalex-stripe What do you think? I'd like to keep the 1:1 mapping between existing methods and API requests (i.e....

Hi @mrfreitas, thanks for the suggestion! I don't think we'll be able to tackle this immediately, but I'm going to tag this as `future` and we'll keep this in mind...

Hi @linkyndy. For historical / backwards compatibility reasons, the `retrieve` method has a different signature than other methods that affect a specific resource. The `retrieve` method expects an `id` and...

I know we haven't given any updates on this, but just wanted to say that this is still on our radar. For API keys specifically, you can specify the API...

Hey everyone, thanks a lot for the feedback. We're considering releasing a new major version soon, so this is very helpful. @Nek- I'm considering making the following changes: - rename...