Skip to content

Move HTTP Streaming computed properties into one prop

What does this MR do and why?

Previously there was a bunch of computed props that depends on isInstance and each required computation. Moving this all into one prop to reduce computational effort and centralise variables.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #419735 (closed)

Edited by Nate Rosandich

Merge request reports