Joey Marshment-Howell

Is there any workaround for this? This would be a great feature that would allow us to really easily create chained integration tests using Insomnia. For my use case, just...

Closing because this cannot be reproduced!

I'd like to add a related thought here, but maybe it's more appropriate as a separate ticket. Currently we have some "nested interactions" that I find both error-prone and not...

Moving to the icebox for now because it's not a clear priority

> "primary" | "darkBlue" | "action" | "grey" | "success" | "error" | "warning" Can I suggest that we only use semantic names, not names of colors (`"darkBlue" | "grey"`)?...

@krishnaglick any update on this component? Would be great to get it built asap, because it is a building block for some other UI library components.

@chandlerprall are we able to close this issue now? Looking at https://github.com/airbytehq/airbyte-platform-internal/pull/7709/files

@Pegase745 sorry to hear that! FYI I have not found a solution yet. Right now we're just not testing `react-select` inputs inside of `formik` because it blows up our test...

After reading [this issue](https://github.com/authts/react-oidc-context/issues/474), it seems like your position is that changing settings dynamically should not be supported.