Sébastien Levert

We absolutely should look into this. The SDK experience will be greatly improved!

Thanks for adding me to the converation @nikithauc! @moinkhanif, can you share with us the full Graph API endpoint this call generates? I want to be sure I have an...

With my repro, I'm getting a similar result. I tried with both Graph Explorer and Postman to ensure this was not SDK related. `GET https://graph.microsoft.com/v1.0/me/calendarView?startDateTime=2020-01-01T19:00:00+05:30&endDateTime=2022-01-01T19:00:00+05:30` And I'm getting the following...

Coming back to this topic. It seems like the + sign needs to be URL encoded. I was able to execute the query using the following : `GET https://graph.microsoft.com/v1.0/me/calendarView?startDateTime=2020-01-01T19:00:00%2B05:30&endDateTime=2021-01-01T19:00:00%2B05:30` @moinkhanif...

Absolutely agree here. The same typings should be used by a user leveraging Core and the Service Library. This means it should be delivered via its own package for users...

Correct. Basically the data shape.

Actually... SDK developers should not know that they need to encode. It's not their responsibility. I tend to think we should do the heavy lifting and offer a consistent experience.

@waldekmastykarz question stays valid though. When to use core vs. when to use service library when you are looking at "only" the `.api()` approach to call the API. This is...

@waldekmastykarz the service library has all the features of the core. So you will absolutely be able to add, modify and play with the middlewares. So as you say, we...

Agree with your last statement. It would be called the Graph SDK. Nothing specific to "Service". Same we do with other languages.