Explore >> Select a destination
|
You are here 
|
codedrivendevelopment.com | ||
| | | | |
blog.davemartin.me
|
|
| | | | | A critique of modern React, specifically the hooks API, and an explanation of why it's insufficient as a web development framework | |
| | | | |
jmmv.dev
|
|
| | | | | Dependency injection is one of my favorite design patterns to develop highly-testable and modular code. Unfortunately, applying this pattern by taking Rust traits as arguments to public functions has unintended consequences on the visibility of private symbols. If you are not careful, most of your crate-internal APIs might need to become public just because you needed to parameterize a function with a trait. Let's look at why this happens and what we can do about it. | |
| | | | |
chrisfrew.in
|
|
| | | | | Unifying Gherkin, Cucumber, Jest, Cypress, Detox for a one-stop full pyramid testing suite. | |
| | | | |
reactnative.dev
|
|
| | | JavaScript! We all love it. But some of us also love types. Luckily, options exist to add stronger types to JavaScript. My favourite is TypeScript, but React Native supports Flow out of the box. Which you prefer is a matter of preference, they each have their own approach on how to add the magic of types to JavaScript. Today, we're going to look at how to use TypeScript in React Native apps. | ||
