Should updateXXX methods pass a single object or array of objects about xero-openapi HOT 2 OPEN

As a developer and long-time consumer of the Xero API, and as I've commented in the linked post above, I definitely think accepting a single object instead of an array with a single object inside will be more user friendly for developers. I would even go as far as just passing in the ID only, instead of an object with an ID, because that is the only thing the API really needs at that point.

The Stripe API is a good example of how this is done really well, and you simply pass in , and you're done. No need to think about convoluted array structures, making sure your objects keys are correct (was it invoiceId, invoiceID, InvoiceID, invoice_id, or ....?), or having to look up other implementation details.

Less is more, and allowing us to pass in less information into the API to get the same outcome will improve the legibility and usability of the API drastically.

from xero-openapi.

Personally I agree with @adamreisnz

Less is more.

This is one of the reason I have created my own API to front end the Net-Standard API . I have simplified methods to get an invoice and I retrieve LISTs of objects and not an object with a list.

So in short I am normalize the API in the way I like to use it.

from xero-openapi.