mike douges
mike douges
Take this code: ``` export function Component() { return } ``` When switching to another component the background is never unset. This only happens if the initial component opened sets...
https://blog.inkdrop.app/code-signing-certificate-for-indie-developers-564f86492957
Haven't replicated this but it's something I saw, will come back later with more info if it happens again.
This ends up being frustrating with code-first development as you're setting component controls, iterating, and then it gets cleared out. For component controls / provider controls their state shouldn't be...
Meaning anything that is grabbing the camera to use for graphics, e.g. billboarding, won't work as expected. This is technically a feature right now, you can put your own camera...
I don't know how to replicate it, but it happened to me once where I was updating the config and nothing was changing, but then when I reloaded VS Code...
Feedback from [Discord](https://discord.com/channels/1077806513009197156/1250573358429634641/1331872763300024391) community: > Can I suggest two minor QoL improvements? (Not sure if exclusive to the VSCode extension or if it applies to the stand-alone version as well)...
- Images via imports aren't the same, e.g: ``` import perlin from "@/shaders/material-steam/perlin.jpg" ``` Results in a string in Triplex, but an object in Next.js. - Router links / context...
Only userland objects should be highlighted. The grid isn't one of them.