Now even though that may sound like a lot of work, it isn’t a bad thing! These tools and high-level frameworks can save you a lot of time and trouble.
Today we’ll talk about TypeScript and how you can work with it’s types.
“Data-driven web applications”. That’s what most of us are building. That means our application takes in data, processes it and then displays the processed (and / or raw) data in some form.
If you’ve been developing websites for a while, you’ve probably had to deal with DOM manipulations of some sort. These DOM manipulations aren’t straightforward and the code that we end up with isn’t very pretty. Libraries like jQuery made DOM manipulation easier, but the resulting code still looks clunky.
Displaying data isn’t the only challenging task. Dealing with user inputs and updating values can become tiring very quickly.
That’s exactly why we have front-end frameworks like Angular. They make it easier for us to mainpulate and bind data.
Recently, we spoke about the basics of routing with Angular 2. We covered everything from configuring the router to adding basic routes to your application. If you’re just getting started with Angular 2 routing, glance over the other article.
We’ve equipped our users with the ability to move around our application. They can see different components based on the route they are on. We can link our users to different parts of our application with
RouterLink and highlight those links when the route is active with
We’ve also covered how to add routes in child modules instead of having a massive
But there is so much more in a data-driven application. Many applications move from list view to item view – where a user selects one item from a list and is shown the details of that item in a new route. This means we need to figure out how to send arguments in our routes and read them in the components.
Strap your coding gloves on, because we’ll be covering that and a lot more!
Did you sit in one place all day, every day last week? Or did you make a few trips to work, the grocery store or the theater?
If you aren’t locked up in your room most of the day, chances are you move around a lot.
Users are no different. When they’re on your next killer web application, they are going to update their profile picture, place an order, monitor their stats or just change their settings.
We wouldn’t want to show them all this information in one place. That would just cramp things up. Imagine cooking, eating, working, and sleeping on your study desk. Not so much fun…!
That’s why our web application needs different places to show the user different sets of data.
But the user can’t get there all by himself. We need to show him the route.
All applications have some amount of asynchronous code. Imagine if you had to wait for every application on your computer to complete a task before you could do something else.
What if you had to wait for all the posts to load on Facebook before you could see your Facebook home page.
That’s just not how the internet works. Everything is asynchronous. Google Analytics is asynchronously tracking your every move as you read this article…
When we started to learn to code, we were taught to write in a particular way or style. In Angular, you have to use different types of directives as part of the language. Today we are showing you three ways on how to use those different types of directives.
Every day, hundreds of software companies strive to improve their products. As developers, engineers, and managers, we are faced with so many challenging decisions such as coming to terms on app architecture, structuring teams, delivering new features or fixing a bunch of annoying bugs.
We don’t complain. We love it!
Thanks to thousands of open source projects, writing code has never been better. There are so many packages that we can just pull into projects. We no longer need to reinvent the wheel.
But we still need to answer a few fundamental questions when we start off with any new project:
Which framework should we use?
How should our app be structured?
How can we ensure consistent UI across our products?
End to end testing is a somewhat polarized subject in software engineering. While, some argue against it with valid points, we still think they are an important tool to have under our belt. In this article, we will go over a few of the other testing ways, and dig deeper into the why, and how of end to end testing for Angular 2 applications.
Before we dig deep if you aren’t familiar with the different levels of testing, here’s a quick overview.
Well, let’s lay down some facts. The Angular team has been on the forefront of this innovation. They have been one of the pioneers in providing the framework to build large scale applications. It now embraces the move to ES6 and TypeScript, and it’s here to stay.
But the fear and concern are still understandable. Adopting and upgrading to Angular 2 can be a big undertaking. Specially if you are responsible for an entire codebase.
There are so many issues that can pop up when switching to Angular 2 in a production environment. So the question we need to ask ourselves is –
“Is upgrading to Angular 2 worth it?”
Testing is important to building solid, production-ready applications. Today we’ll be discussing Angular 2 Testing, but regardless of the language, framework, or application we are building, having a solid test setup is crucial to know if our applications are functioning properly. We might accidentally introduce a bug when adding functionality that we won’t ever know about until we get an angry customer email.
Often times we’ll skip testing because it takes a lot more work to write our tests than actually writing the code and who wants to write tests anyway when we know they are going to break in the first place? However testing is incredibly vital to the health of a solid application, so we introduce this short guide on how testing doesn’t need to be a painstakingly-long process. By the end of this article, you’ll see just how quick and easy it is to get started with Angular 2 testing. Continue Reading…