I am intentionally making this issue specific but I assume it could be expanded to include much more of the API.

Problem

I do not have the entire Prisma Client API perfectly (let alone roughly) committed to memory.

When I go to use it to query for many results the operations tell me nothing about what and why they will do. I only have types to work with.

I don't want to open my br

Platform

Operating system and version: Windows
OBS Studio version: 26.1.1
OBS Log file: N/A

Expected Behavior

EITHER:
a) Multiple transform panels open for different sources and closed manually (not preferred)
b) The transform panel shows the appropriate information for the respected layer selected

Current Behavior

The transform panel sometimes shows the newly selected item

The current WHATWG URL parser implementation is written in C/C++ and incurs a fairly significant cost crossing the JS/C++ boundary. It should be possible to realize a significant performance improvement by porting the implementation to WASM (similar to how the https://github.com/nodejs/undici project has seen a massive performance boost out of moving llhttp parser to wasm).

If someone wanted to