In Sketch 52, we introduced an exciting new feature —Data. If you still haven’t read about it, be sure to check our release blog post, or take a look at this great intro video by Peter Nowell, which is part of his new UX Design in Sketch course:
This new feature makes it really easy to bring data into your designs, and solves the most common use case—“just give me something random”— as painlessly as possible.
But what if you have slightly more complex needs? What if don’t want your data to be random, but totally predictable? …
Adventures on the land of logging errors from everyone’s favorite design tool
I’m in the process of building a TextMate bundle for Sketch Plugin development. I wanted to have access to detailed error information, so I could use that to move the cursor to the offending line when there’s an error.
Problem
Currently, when we run a command in Sketch and it doesn’t work, we receive no information about what, where or why it happened on Console.app.
There are two workarounds for this. None of them are perfect, but they’re definitely better than no error reporting…
- We can wrap our code on a try { } catch { } call. This is the less painful method, and it’s probably good practice anyway, but it doesn’t give us the whole error information that JSTalk provides (i.e: …
About
