Sébastien Levert

This seems more related to the internals than extensibility. Unless you'd want developers to identify their own ways of handling dates, in the mentionned issue. In our case, I think...

As the RequestBuilders (the fluent part of the API) are auto-generated and might not exist or have "duplicates" (think client.me.messages and client.users[""].messages), should we even think about extending the fluent...

Thanks for pursuing this discussion @baywet! Can you share examples of how this code would be used by a developer? I have a bit of a challenge to grasp it...

Both! I think I'd love to see how one would build an extension, and how it integrates "within" the SDK for the client developer to build their app.

To your point @pschaeflein, the `Colleagues` scenario is what triggered this whole conversation. It can be done today, but can it be done tomorrow with our generated approach to our...

Just as an idea and see if that even makes sense. Could Interfaces and Classes have the same name and the interface could implement the "Aliased" model? This is definitely...

I think the goal here is to have models being exported so you can use their types, but will people really use RequestBuilders as types? Or use them as ways...

It would be a great way to offer customization!

Hello @ThomasPe. Can you expand a little bit more on this topic? I'm curious as today, the component will strip users already selected in the PeoplePicker. Is it that it...

Absolutely makes sense! This is a great example that definitely sells the use case! We'll discuss internally on the next steps and see how we can make them as close...