I wouldn't say its a bug, since its not like they are trying to copy all entries from HttpContext.Items and then just missed some of them.
But definitely a feature request. Question is then though whether the copying is a one-way street, or if any changes to HttpContext.Items from within a MVC Function should be propagated back to the original HttpContext. The same goes for Cookies which i have wasted some hours on, trying to set cookies from within a MVC Function.
Maybe create it as an issue on the GitHub Packages page. And if Composite is not responding, consider moving to the Community Edition of MVC Function, which was created by me and RogroGengu and predates Composites version by almost 2 years, and was what Composite basically copied into their own. The code for it lives here now https://github.com/burningice2866/CompositeC1Contrib/tree/master/Rendering.Mvc and i'm up for fixing and discussing all issues and suggestions.
But definitely a feature request. Question is then though whether the copying is a one-way street, or if any changes to HttpContext.Items from within a MVC Function should be propagated back to the original HttpContext. The same goes for Cookies which i have wasted some hours on, trying to set cookies from within a MVC Function.
Maybe create it as an issue on the GitHub Packages page. And if Composite is not responding, consider moving to the Community Edition of MVC Function, which was created by me and RogroGengu and predates Composites version by almost 2 years, and was what Composite basically copied into their own. The code for it lives here now https://github.com/burningice2866/CompositeC1Contrib/tree/master/Rendering.Mvc and i'm up for fixing and discussing all issues and suggestions.