V10: No interfaces. Forces poor coding

[TonyValenti]

Hi All -
I've been taking a look at moving our code to the V10 codebase but I'm seeing a lack of patterns that will really make moving forward very hard for us.

In the Box API, there are lots of kinds of responses and objects that share properties.

In V5, there were objects like BoxCollection, but in V10, there is no such foundational class or interface.

Can you please adjust the code so that there are base classes/interfaces that we can implement around?

[mwwoda]

Hi @TonyValenti

Thanks for submitting the feedback.

Our v10 SDK is almost fully generated based on Box Open API specification. The BoxCollection in our previous SDK was used to map the List responses from the API to C# classes. But actually Box does not standardize API response when the list of entities is returned. It could differ based on endpoint. For example

https://developer.box.com/reference/get-groups - order_by present
https://developer.box.com/reference/get-folder-locks - order_by not present

It would be quite difficult to provide single interface that would work in every scenario. Fortunately, we plan to support pagination by the SDK in near future. In the current implementation, we have we have interfaces for the response there - similar structure to the BoxCollection present in the old SDK. Paginated response usually follow API standards more strictly. They would allow you to write the code in more generic way. I'll pass your feedback to the team to see if we could potentially somehow address functions that does not return paginated response.

[TonyValenti]

Thank you so much! I will sit tight and wait for a future update.