Alexander Vassbotn Røyne-Helgesen

@ipaintcode The road you've started to tread has many pitfalls :P I've been trying to bridge the designer/developer waters for a very long time, and I always come to the...

@caoimghgin I'm all for a spec and naming convention, but I think a DT spec _should not_ dictate **A** naming convention, but rather dictate that a naming conventions MUST be...

Need to bump and check! 

with `0.4.9`I now get: ``` (!) Plugin node-resolve: Could not resolve import "@lyrasearch/lyra/dist/esm/stemmer/lib/no" in /home/alexander/Workspace/knowit/client/svv/dtm/src/lib/search.js using exports defined in /home/alexander/Workspace/knowit/client/svv/dtm/node_modules/@lyrasearch/lyra/package.json. ``` instead. Is there a breaking change?

@adrai thanks for the suggestion. I've tried that with no avail sadly :/ Tried to include it in the test, in the test setup file, the `renderWithI18NContext` wrapper and in...

You need to check if space is pressed first. This is how I solved it: ```typescript let spacebarPressed = false; const handleSpaceBarKeydown = (e: KeyboardEvent) => { if (e.key ===...

If I remember correctly, there's a way to get gists imported in codepen.io. I checked that out a few months ago, but now I've forgotten it :(

If I may, I would like to address the elephant in the room; Why do we have to force a unit value in the spec? Maybe I'm wrong here, but...

Well, I've experienced that you can have more than one unit in a component. What if the spec dictated a default unit, and then add option to have that overridden...

Working with Frontend since 98, and accessibility since validation and section 508 came around, you cannot exclusively have rem/em. This article sums it up https://www.joshwcomeau.com/css/surprising-truth-about-pixels-and-accessibility/