background preloader


Facebook Twitter


Thinking React. React Visual Studio. React Native. Props. Mantra. Learning. GraphQL. Flux. Component. Blog. Adding A Robust Form Validation To React Redux Apps. Adding A Robust Form Validation To React Redux Apps Form validation is vital because it helps with the UX. It helps user know that there is something wrong with what they’ve entered or if they’ve missed something and so on. A “robust” form validation helps with (at least): Client-side Validation: e.g. Check empty fields, password length etc.Instant Server-side Validation: e.g. Instantly check server if username is unique upon blur.OnSubmit Server-side Validation: e.g. Check server after submitPrevent Duplicate submission: e.g. But implementing such a form validation is a lot of work in any framework including Redux apps. Use libraries 🎉😀! OK, Let’s see how to implement all those scenarios by taking using an example app. Note: Click on the picture above to Zoom and read. I’m will use the same multi-page blog app from “A Guide For Building A React Redux CRUD App” Source code: Live App: 2.

Angular 2 versus React: There Will Be Blood. Angular 2 versus React: There Will Be Blood Angular 2 has reached Beta and appears poised to become the hot new framework of 2016. It’s time for a showdown. Let’s see how it stacks up against 2015’s darling: React. Disclaimer: I enjoyed working in Angular 1 but switched to React in 2015. Alright, let’s do this. You’re Comparing Apples and Orangutans! Sigh. Choosing between Angular and React is like choosing between buying an off-the-shelf computer and building your own with off-the-shelf parts. This post considers the merits of these two approaches. Angular 2 Advantages Let’s start by considering Angular 2’s advantages over React. Low Decision Fatigue Since Angular is a framework, it provides significantly more opinions and functionality out of the box.

Angular offers more opinions out of the box, which helps you get started more quickly without feeling intimidated by decisions. I admire how the Angular core team has embraced TypeScript, which leads to the next advantage… Reduced Churn {myVar} Angular Directives Mapped to React. Ng-class React doesn’t provide something like ng-class, but there is a great library called classnames that does the same and more. Install it: npm install classnames Import it however you like: import classNames from 'classnames' ; var classNames = require ( 'classnames' ); var cx = require ( 'classnames' ); Then it supports things like this (from their docs): And use it similarly to ng-class (also from their docs): var classNames = require ( var Button = React . createClass ({ // ... render () { var btnClass = classNames ({ }); return < button className = { btnClass } > { this . props . label } < /button>; } }); ng-repeat <ul><li ng-repeat= "item in items" > {{ }}</li></ul> In React, use Array’s built-in map function to turn an array into elements.

Pay attention to the special key prop passed to the li. You can write it as a “stateless functional component” with a little help from ES6’s destructuring and arrow functions, the syntax is even lighter: ng-click ng-switch ng-style ng-change. Blog Posts. Compilation of open source/boilerplate React Meteor apps : Meteor. Dan Abramov - Live React: Hot Reloading with Time Travel at react-europe 2015. Dear Templating — Sincerely, JSX Part 1. Dear Templating — Sincerely, JSX Part 1 Surprisingly, the biggest complaint I hear about JSX is along the lines of It’s such a tight coupling to the DOM Well, not really, it is just a declarative syntax to describe components in a tree…Virtual?

DOM? A team of designers can freely modify templates without worrying about breaking anything or even touching the logic I know designers buying into JSX because they truly enjoy stepping outside of what they know. It’s not like designers understood Mustache or Handlebars the first day they saw it! If you’re a designer check out this article. You have to port/reimplement all the stuff that JavaScript has already solved to your templating language.

Ding, Ding, Ding! But First…They’re not so different… Templating and JSX are considered Domain Specific Languages (DSL). What is Templating? Templating refers to the client side method of binding data to views. How does this work? Templating languages work like so: <h1>Hello World</h1> What is JSX? Don’t fret! {{! Enaqx/awesome-react: A collection of awesome things regarding React ecosystem. ES6 + React part 1. From Blaze to React 04: Layouts & Redirects. We’re pushing forward in our quest to slim down our router code. After getting rid of subscriptions and data context declarations, it’s time to take on redirects. Thinking About Redirects A “traditional” redirect sends the user to a new route, but a better and less disruptive pattern is to keep the URL the same, and instead just switch out the contents of the template. This type of “in-place” redirect is what we’ll use.

Another factor to consider is that most redirects rely on subscription data –typically the current user– to do their job: after all, you can’t know whether to let someone through or not until you know who they are. Redirecting commonly happens when a user tries to access a route without the proper rights. For example, here’s what the isLoggedIn filter originally looked like (warning: ugly code ahead): As you can see, a lot of the complexity comes from the fact that the filter relies on subscription data from the Meteor.user() object. Template-Level Layouts Wrapper Templates. GitHub - yongxu/react-DnR. Hot Reloading in React. Hot Reloading in React or, an Ode to Accidental Complexity React Transform is an experimental project I started after giving the Hot Reloading with Time Travel talk at React Europe. My goal was to bring a live editing environment that preserves component state and handles errors gracefully to as many React users as possible.

By all reasonable metrics, React Transform has been a success. I would even say it has been way too popular for such an experimental and unpolished piece of software. I am sorry about this, as I had no time to focus on the experience of setting up the tool. In fact I’ve come to realize that it is not a viable solution in the long term, and I plan to sunset React Transform in a few months in favor of a different project. In this post, I will explain how I came to this conclusion, as well as describe my journey in understanding how hot reloading can be implemented, and the challenges I faced, in more detail than I did before. React Transform is a mixed bag. Disclaimer. How we unit test React components using expect-jsx | Milliseconds Matter.

React was designed to solve one problem—how to build applications with data that changes over time. Considering the as-you-type search experience offered by Algolia wherein whole results pages, hits and refinement links alike, are updated at each keystroke, React was the obvious choice when we needed a tool to build out our new library of UI widgets: instantsearch.js. We quickly struggled, however, with the unit test best practices for React components. We jumped from Github issues in facebook/react to blog posts and but couldn’t find a clear unit testing strategy.

Now that we’re happy with our testing stack, we wanted to share it with the community to hopefully make your testing process a bit easier. How to test a React component Before digging into the whole testing stack, how do we test a React component? If you search for “React unit testing”, you’ll quickly find the popular React discussion—What’s the preferred way to test React.js components? Not too bad. Sources. Is There Life on React Planet? - XB Software. When a new development technology gets your attention, many different criteria allow you to judge if it’s good enough for gaining benefits for your business.

Fast development speed, high-performance rate, good looking user interface, the possibility to develop applications that look and feel good on different devices. Depending on which feature is more crucial for you, you can prefer one programming language or library over the others. But here’s another important thing that you should not forget while choosing a suitable library for your project. The ecosystem. There’s no such thing as a silver bullet when we talk about the web development. One should not expect that a single library will solve all the possible troubles. And here’s when the ecosystem comes to the rescue. The more ways of using React is available, the more issues you can solve with it.

React Libraries Overview As an example, we’ll discuss four libraries that realize different approaches to the application development: MobX: Ten minute introduction to MobX and React. MobX is a simple, scalable and battle tested state management solution. This tutorial will teach you all the important concepts of MobX in ten minutes. The core idea State is the heart of each application and there is no quicker way to create buggy, unmanageable applications then by producing inconsistent state. Or state that is inconsistent with local variables that linger around. Hence many state management solutions try to restrict the ways in which you can modify state, for example by making state immutable. But this introduces new problems; data needs to be normalized, referential integrity can no longer be guaranteed and it becomes next to impossible to use powerful concepts like prototypes.

MobX makes state management simple again by addressing the root issue: it makes it impossible to produce an inconsistent state. Conceptually MobX treats your application like a spreadsheet. First of all, there is the application state. A simple todo store... Becoming reactive That's it! Your name: Pourquoi pas ReactJS ? A l’heure actuelle, AngularJS s’impose comme la référence des frameworks web. Son approche “full-stack” (c’est à dire qui contient tout le nécessaire pour construire une application single-page ou “SPA”) séduit et son architecture présente de vraies bonnes idées (modularité, injection de dépendance, …). La formation Zenika marche d’ailleurs très fort. Le framework s’appuie sur sa communauté et son écosystème de librairies dont certaines sont devenues incontournables (UI-router, UI-Bootstrap, angular-translate, etc.).

Mais au-delà de l’écosystème AngularJS, il y a celui du Javascript, plus vaste encore et dans lequel se trouve le produit d’un autre géant du web : ReactJS. Une autre typologie de projet AngularJS est très orienté application de gestion, c’est à dire des écrans de liste/détail, pour faire du CRUD sur des entités métier. Un framework orienté Composant ? Or de l’aveu même de l’équipe AngularJS, l’API des directives n’est pas évidente et leur utilisation peu intuitive. Un état, Productive Rage - Writing React apps using Bridge.NET - The Dan Way (from first principles)

15 March 2016 I've had a request from someone to write about how I think that someone from a .net background should write a web-based application. The short answer is that I strongly believe that using Bridge.NET with React, using a Flux-like architecture is the way forward. I think that React changed the game by trying to introduce a way to write applications that addressed the big challenges, rather than what many of the other frameworks did, which was to try to make some aspects of development easier but without tackling the underlying problems.

We're going to be using these technologies to create some big applications where I work and some resources as to how best to do this will be valuable. I'm going to try to roll this all together into a short series of posts about creating Bridge / React / Flux apps, where I'll try to start from the simplest approach at each point and only introduce something new when I can explain why it's valuable. From the very start React components <! React and the economics of dynamic web interfaces - NCZOnline. I've been doing web development since 2000, and in that time I've seen eras marked by libraries and frameworks come and go. The Ajax era began around the same time as the jQuery era began, the Backbone era began several years later, and the React era really began about two years ago. Each of these eras brought with it a new realization about the way we can build dynamic web interfaces based on the tools available. jQuery made it clear that browser abstractions and CSS querying were important to developers, Backbone introduced the concept of client-side architecture to many, and React enables the creation of UI components instead of templates.

There are plenty of blog posts, talks, and videos touting how React works and why it's good for web development. There's been a lot of discussion around the virtual DOM, embedding HTML into JavaScript with JSX, organizing the UI into components. The economics of dynamic web interfaces Make only small changes. React changes the equation Conclusion. React-virtualized. React.js Conf 2016 - Aditya Punjani - Building a Progressive Web App. State of React and CSS — KADIRA VOICE — Medium. Recently, I started to work on a project that helps us to develop UI components isolated from the main app. Initially, I assumed everyone would write CSS in JavaScript with React. After a while I realized that it’s not fair to assume that everyone would write CSS in JavaScript. CSS is a land of choices.

In this article, I will share what I found from the research. Let’s get started. 🤓: Wait. Can I have a look at the tool you mentioned? It’s React Storybook. How do we use CSS? The first question we should ask is how we are using CSS. Frontend Developer The role of the frontend developer is to implement business functionalities. Frontend developers don’t usually worry too much about CSS. UI Designer The role of the UI designer is to build great User Interfaces that customers love. Basically, UI designers need to make sure that the design they create in Photoshop is what is actually implemented. They usually care a lot about CSS and work with the components created by the Frontend Developer. Yes. The Elevator Pitch for React -Telerik Developer Network. A lot of people are offering up an overview of React. In this article, I’m going to toss my thoughts into the mix by providing my own overview.

It’s my goal that by the end of reading this, you’ll firmly understand React from a ten thousand foot view. React is… React is a JavaScript tool that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. I could ramble on trying to express in words what React is, but I think it best to just show you. So let’s just jump right into it. Using React to Create UI Components An HTML <select> is not unlike a React component and is a good place to start learning about the nature of a React component. When a browser parses the above tree of elements, it will produce a UI containing a textual list of items that can be selected. The browser, the DOM, and the shadow DOM are working together behind the scenes to turn the <select> HTML element into a UI component. Defining a React component instead of this: Conclusion. Unit Test React Components in Meteor — All About MeteorJS.