Nic Barker
Nic Barker
Hello @JannesN, would you be able to include your OS details & browser version numbers?
Hello @neslib, hello and thanks for opening this issue 🙂 Clay has _almost_ transparent handling of strings, with the only real internal logic being iterating through the string and breaking...
@mikejsavage I totally agree, the inspector hardcoding colour values was a mistake. I wanted to make sure the data type was flexible enough to support formats that use 4x floats...
Thanks for reporting this, will get it fixed up 👍
Thanks for reporting this! Should be looked at in the next week or so.
Hello! Firstly, I completely agree with your assertion that we need a local context-aware way to auto generate IDs. At present it's quite painful to have to uniquely everything in...
This was addressed in https://github.com/nicbarker/clay/pull/27 but I will leave it open until I've updated the `README` to include documentation of the new feature.
Yep, you're describing pretty much my exact line of thinking - a single macro that can be configured with whichever features. There is a little internal work to do to...
😁 Finally wrote the README section for this here: https://github.com/nicbarker/clay/commit/ebeef93c34a393813aaf789f76149ab1f5502bcd
@ColleagueRiley raised a similar point and I think you're right - the ergonomics are likely worth the increase in struct size here 🙂