Open jbostoen opened 4 years ago
There's not likely to be any impact. There's still the option of using OAuth with this library, and if that doesn't work then that's something I'm happy to look into. Older versions of Exchange will still use Basic Auth, so there won't be any change needed there. Also, while I haven't been actively working on php-ews
, it won't be abandoned. If there's things that people want that are easy to do, bugs that I can tackle or PR's that people have written I'm still more than happy to work on it. That being said, a lot of the issues that are open at the moment aren't issues that I can tackle easily.
As for deprecating EWS for Microsoft Graph, I didn't even know EWS was getting feature updates anyway. The goal of this library was never to be up to date with the latest and greatest features of EWS to begin with, or even to be feature complete with older versions, but rather to provide a simple wrapper around the EWS SOAP API with a way to create the request objects in a compact and easy-to-read manner.
That's the primary reason why all methods are public and I try to keep the functions light and easy to read. The idea was always that there'd be some functions for the simple, obvious things and then if you wanted to do anything more involved you'd construct the message yourself with getClient()
.
Thanks for the quick reply!
Will there be a lot of impact by this announcement?
Basically: