Skip to content
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

What does the msgraph-sdk-python mean for the future of this project? #1032

Open
will-byrne-cardano opened this issue Dec 21, 2023 · 3 comments

Comments

@will-byrne-cardano
Copy link
Contributor

First off, I want to start by saying I love this library. It has helped me so much with many projects at my work - thank you!

I stumbled across the msgraph-sdk-python, developed by microsoft, and I was wondering if this has any impact on the future of this project?

@alejcas
Copy link
Member

alejcas commented Jan 8, 2024

I wasn't aware of that project.

O365 it's a little bit more than just a wrapper around MSGraph. It can handle multiple apis (like the old Office 365 api and ms graph api by implementing protocols) and sort things out by code when the api does not provide that functionality (like sorting arrays that ms graph does not).

Also it interconnects API objects (drive items with mail items, contacts, etc...)

And many more little things.

However, for the moment no further development of O365 is taking place other than users pull requests, as I currently don't have the time to spend on this project.

@will-byrne-cardano
Copy link
Contributor Author

Thanks for the response, and clarification. Glad to hear it won't be going anywhere any time soon.

If you need any help implementing new features/functionality - or even just adding to the docs - I would be happy to get involved. I have a fair amount of experience with MSGraph but not much with the other protocols. I use this library extensively so would be good to give something back :)

@alejcas
Copy link
Member

alejcas commented Jan 8, 2024

The main issue with O365 it's that we use a custom connection procedure. I thing It should use msal so we drop the custom procedure.
That way it resolves a lot of connectivity issues and adds more methods like certificates and etc. that we currently don't support.

That would be number 1 todo.

Other than that:

  • The upload for files into drive should be easier
  • The sharepoint and excel is lacking a ton of functionality
  • plus other features like MS teams, etc.
  • Docs are not up to date and mainly in the project readme. However this requires a lot of effort (+ maintain). I would prioritize features over docs for the moment

If you want to collaborate into this issues or another ones you are very welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants