Apollo has given us freedom and happiness when it comes to managing our data coming from the server but we still had to write code and sometimes a lot of it to manage our local state?
Well, what if we managed it with queries too? Sounds too awesome right?
Let's learn how to do this with apollo-link-state
During the talk I will explain what recent browser technologies have emerged and how you can apply this to make the experience of the user better. This won't mean that you need to drop support for older browsers, these improvements can be used to enhance the experience instead of replacing it.
This talk is going to focus on some advanced patterns in building your react components. More over we do not know what the best way to do things and we end up feeling stressed out. To release your stress let talk you can make use of some patterns that worked for us best and will work for you as well :)
It is not easy to know what will truly deliver lasting value to your development as opposed to what is merely a passing fad or what will fail to live up to its hype. My team at PayPal has been excitedly using GraphQL in many of our new apps. We love the idea of a single endpoint providing frontend developers access to the great multitude of PayPal services.
In our excitement for GraphQL, we also implemented Apollo Client and React Apollo into our app. After all, the boilerplate and heavy weight of Redux has been much maligned, and we saw and easy way to significantly reduce the amount of code we wrote, all the while utilizing the sleek new utility for state management that Apollo Client provided.
However, we soon realized that we had made a mistake and pre-emptively jumped into Apollo Client. The fact of the matter is, Redux is much more than simply state management, and we had failed in our original estimation to fully appreciate what Redux gave our app that Apollo Client simply does not.
This talk will explore why we initially were so excited about Apollo Client and why it was our first choice. It will then explain how Apollo Client fell short of our needs, and why Redux is a significantly better choice for most larger applications. Finally, it will hope to inspire a reappreciation for Redux.
Testing should make us confident. Confident that our software does what we think it does, and that it will continue to do so as we pile up features.
But testing UI components rarely breeds confidence. Instead, it often makes us feel angry and unproductive. Let's look the beast in the eye and talk about a set of tools that make testing React components as easy as writing them. We'll learn how to mock component props, state, Redux state, app context from wrapper components, as well as API responses, without copy pasting boilerplate from one test to another.
Behavioral programming simplifies the task of dealing with underspecification and conflicting requirements by enabling the addition of software modules that can not only add to but also modify existing behaviors.
In this talk I will describe how Behavioral Programming concepts can be applied to React. Specifically, I will showcase real-world examples and demonstrate how programming using this new paradigm can alleviate some of the issues that arise when programming with large teams. Moreover I will present a library that can be used to program what I call "behavioral components" using this new idiom.