Hey there, that’s me again and a new post from me! Lately, I worked on the project that generates live documentation of the front-end components for apps built with create-react-app, and this UI development environment is called Storybook. What is the significant purpose for using this tool? First of all, it helps to avoid code duplications and to make it easy to know which components there are already, what they are doing and how they are being used.

Hi, everyone! How is your weekend going? As you know, I prefer learning to code by doing things. So, the last feature I have implemented for the app is the reading of the content from the uploaded (local) .csv file from the user. To do so without a server or any back-end—is a challenge. To make things work properly in React+Redux, I have created the following component: const ImportFromFileBodyComponent = () => { let fileReader; const handleFileRead = (e) => { const content = fileReader.

There are many possibilities how to remove multiple items from the array with JavaScript. So in this tutorial, I am going to share my approach to delete function with React+Redux. It’s front-end shorts, and I am trying to highlight the most important information. Thus, just let’s have a look at the significant code snippets with explanations: I have created the action: // expenseActions.js export const t = { ... DELETE_EXPENSE: 'DELETE_EXPENSE', .

Today I am going to tell you how to get JSON data from the Rest-API to UI using React+Redux frameworks. In my case, the task looks like: I have a URL, for example: https://api.com/v1/expenses/ which will give the following JSON data, and I want to get this data in my UI. To solve this task, I decided to use JavaScript’s fetch method. So in this way, I shouldn’t rely on any external libraries (given my target browsers are remotely up-to-date).

Hi, everyone! How is your week going? Yesterday I worked with the web application written on React + Redux and had had some problem with the react-router-redux library. In short, the push method (using for navigation outside of components) didn’t work. Firstly, I have tried to set the Route component in the “traditional” way such as with react-router library. That might get the history props. Unfortunately, that also didn’t work. Because of Redux framework.

Let’s continue developing an Interactive ToDo List. Refer to the previous posts you notice that we are almost done with the basic functionality of the application. And today I would like to start the topic about persisting the data and restoring it after refreshing the page or starting a new session on the local machine with React+Redux. Changing into the my-daily-todos project, then to src folder where you find index.js. Here we store all the app’s state in the store variable.

Hi there! I am so happy that you continue developing our interactive Daily ToDo app with me. Today you are going to get to know how to implement a dynamic progress bar that will handle task completing status by percentage for every category. But before moving on, if you are new here, please, have a look at the previous posts. You should start developing app there and then continue with us here.

The most valuable feature set for our Daily ToDo is already done. Today we are going to make an app more functional, separating tasks by categories. We want to be able to categorize task by typing # and category after its title. For example: practice a coding kata #programming. As always, we start with the simple user story and the acceptance criteria: As Bob I want to categorize tasks by adding tag into input So I see which task belongs to which category ## Acceptance Criteria Given there are no tasks And I am on dashboard screen When I finish inputting a new task title And choose the category (tag) for a task And press Enter Then I see the categorized task by tag on the dashboard screen Tag examples: Programming, Sport, Languages, University, Reading, Routine If you are a new reader of the tutorial series and don’t understand what is going on at the moment, then just check the previous posts starting with React For Very Very Beginners

Today we are going to implement the second feature for our app. If you are a new reader, then I highly recommend you to check my earlier blog posts here, where we started our learning journey in React+Redux, refer to the posts complete previous steps and continue with us to develop an interactive ToDo List from here. As you guess from the blog title, the next feature called Complete a task.

Hi, everyone! I guess you are pretty encouraged to start coding our app. Just to remind: it will be an interactive daily ToDo List. Today I am going to explain: what is a user story? Why do we need to write it before implementing a feature? How will we organize and structure an app? What is, actually, a new feature? Let’s start with the first question. In my opinion, user stories are efficient things.