Right we have ./ui/src/vscode-api.ts that assumes VS Code for communicating outside the web view. Maybe that can be called "channel" or "messaging" something like that and only internally detect VS Code, but others in the future.
Apart from that, ./ui seems to use a lot of VS Code specific CSS variables everywhere. I wonder how we can decouple that. Maybe we create our own variable names that map into VS Code for VS Code builds but we allow configuring them some other way too?
Right we have
./ui/src/vscode-api.tsthat assumes VS Code for communicating outside the web view. Maybe that can be called "channel" or "messaging" something like that and only internally detect VS Code, but others in the future.Apart from that,
./uiseems to use a lot of VS Code specific CSS variables everywhere. I wonder how we can decouple that. Maybe we create our own variable names that map into VS Code for VS Code builds but we allow configuring them some other way too?