Closed jaredsburrows closed 4 years ago
I agree, this library is getting very bulky for the average use case. All but a handful are autogenerated according to metadata provided by the Graph API. We are currently working with the API team to enable namespacing. This will let us break up the library into smaller packages that the developer can bring in as necessary. Generating SDKs on demand by the developer is another great idea and we have not done a lot of investigation into this work yet. It would also rely on namespacing to work correctly.
Why are there over 2k files in a single Java package? Are these auto generated? If so, I would highly suggest this be broken down into smaller packages and possibly using an annotation process to only generate the files needed based on the clients needs.
There are way too many methods for this library: http://www.methodscount.com/?lib=com.microsoft.graph%3Amsgraph-sdk-android%3A1.2%2B