-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting a DraftPayment that has been ACCEPTED results in an error #63
Comments
Interesting, thanks for the bug report we'll take a look and report back once we have a fix 👍🏾. |
@tomcoonen out of curiosity, how are you populating |
@OGKevin I don't have any trouble making DraftPayments, modified production example:
The $payment_map I drop into |
Ahhh clever, I was using
😅 Which is not ment to be used for making request apparently but only for responses. Might be nice to use this class for making requests as well 👍. Will add this to my todo list for the near future. |
Yeah this package can get some improvements indeed, but first let's get it working ;) |
FYI @tomcoonen |
PHP: 7.1
SDK Version: 0.12.1
Error:
bunq\Exception\BunqException: Found model "BunqModel" which is not defined. in /vendor/bunq/sdk_php/src/Util/ModelUtil.php:60
As soon as you try to get a DraftPayment that has the status 'ACCEPTED', this DraftPayment will have the 'object' attribute set.
In the Endpoint/DraftPayment.php file is stated:
The current code in ModelUtil.php doesn't allow for this since BunqModel is not a subclass of itself.
Quickly searching the code I think the Schedule / ScheduleInstance has the same error?
The text was updated successfully, but these errors were encountered: