Danny Willem

@sarangan12 We'd love for this GET operation to explicitely define it can return a `null` response so that it reflects in the return type definition (`Widget | null`) The use-case...

@sarangan12 If I manually update the body mapper to set the `nullable` property to true, then this works as expected and my `null` response doesn't get wrapped into a `body`...

I didn't meant the issue to revolve around how to handle 404, this was just to expose our use-case. I think people might want different behavior there and autorest shouldn't...

@sarangan12 Would you be open for a PR for **Option 2** ? If yes, any suggestion? I'm thinking we need to somehow achieve for this `nullable` property to be correctly...

This is a blocker for us to start using the generated library but given this is an open source project we're not really expecting any ETA or something so October...

Looks you guys found the issue a while ago already so I'll close. I've been following the past month's commits and there are really cool updates being done, love it...

With DataStreams the Stream information (id + length) is serialized in the message (which we can't deserialize on the router because the router doesn't have the reference to these objects)....

Closing as we're having another approach that's more "sane" and doesn't require a fork