Content api endpoint is not unified

jorttbv / bunq-client

Ruby wrapper for the bunq public api

MIT License

12 stars 7 forks source link

Content api endpoint is not unified #46

Open romikoops opened 4 years ago

romikoops commented 4 years ago

Based on official bunq api documentation content could have different parents. It means we have to rid of Bunq::AttachmentPublicContent class and introduce new one Bunq::Content which will be designed consistency with other classes via parent resource.

bforma commented 4 years ago

Can you make a PR?

romikoops commented 4 years ago

I will try to do it next week.