Sébastien Levert

Adding more context. We should have a RequestAdapter factory on core that would provide something like this: ``` var scopes = new [] { "User.Read" }; var options = new...

Thanks for reporting this issue. It's something we've heard in the past and we should fix for both functionality but also accessibility reasons. Tagging @gavinbarron on work that was done...

My first comment would be to support it the same way the Fluent UI WC TextField works... https://fluent-components.azurewebsites.net/?path=/docs/components-text-field--text-field Should we be the one to handle all those cases or proxy...

* Investigate moving Electron to the "latest" as a peer dependency

With the newly available support for [HTTP/2 on Graph](https://baywet.github.io/microsoft-graph-http2/), I don't think this will dramatically improve the experience. I would close as not planned.

This is a great idea, provide good developer experience and would be useful on the long run. I would be interested in this capability only if these properties are documented...

This sounds like a great opportunity for a community contribution as a separate module that would ensure availability of both Az and Mg modules. I would not include this as...

This still reproes. @yejuntak can you have a look and propose a quick design change for this one to include label?

This is valid and I could reproduce them during some of my endeavors in the past. I see it even as a compliance / trust issue. This should get fixed...

I would push this further. I don't think you really need a `RequestAdapter` in most cases. You basically should just need an `AuthProvider` IMO. And the rest should magically happen...