undefined | Better HN

0 pointscnp9y ago0 comments

> that it's very easy to write code that will break if you poke it the wrong way

No way. Even in its most basic, untyped form the React model simplifies things all the way down your app pipeline. Errors that used to be common tend to naturally vanish over time.

0 comments

1 comments · 1 top-level

yebyen9y ago

I need to learn React, I need to learn Elm... I don't really know what I'm talking about, but on the internet nobody knows you're a dog.

We have some fairly sophisticated JavaScript that is part of our app, but we haven't drank any of the modern JS kool-aid yet, the only validation we're really using is a suite of feature tests written with Cucumber and Selenium/Chromedriver.

So if you have some JavaScript and it is functionally important to a feature that you've tested, it will show on the CI result if it's broken... but if there's a JavaScript error during the test that didn't stomp on the behavior tested by the feature, you'd never find out about it unless you happen to be watching the Inspector console at the time.

j / k navigate · click thread line to collapse