rarwe.tar.gz

Ember

Ember-copy

ember2

embercss

rarwe

Ember-copy-5yvdqv

Ember-copy-5yvdqv-copy

Ember-Acceptest

Ember-Acceptest-copy

Ember-unitest

rarwe-copy

Ember-Acceptest-challenge

Ember-helper-challenge

In this course, you begin with an introduction to Ember.js, a JavaScript framework for building client-side applications.

After that, the course guides you through the steps of building a real application so that you can see how the concepts are applied in practice. You'll learn about the building blocks of Ember one by one, in a way that crushes the allegedly steep learning curve of the framework.

The application will get shinier (and/or more robust) with each chapter. By the end, we will have a decent app, and you'll have a great new skill you can add to your resume.

Developing Robust Ember.js Applications

## How error subroutes work
Error subroutes are activated when a model hook throws an error, either because the backend returned an error response or because the application code, itself, ran into a problem.

Error subroutes work exactly the same way as loading subroutes:

* An `error` event is fired on the route where the error was produced.
* The default behavior is to render an `error` template on the level of the route that triggered the error.
* The entire Ember arsenal is at our disposal to implement a custom behavior. It is just a matter of implementing an action handler for the `error` action in the route.

It only takes a template to show an error message when loading a particular band does not work as it should. Let's create another template:

```shell
ember g template bands/band/error
```

We can display a similar panel, as we did for the loading template, with colors that indicate something slightly bad has happened:

# How error subroutes work
Error subroutes are activated when a model hook throws an error, either because the backend returned an error response or because the application code, itself, ran into a problem.

Error subroutes work exactly the same way as loading subroutes:

* An `error` event is fired on the route where the error was produced.
* The default behavior is to render an `error` template on the level of the route that triggered the error.
* The entire Ember arsenal is at our disposal to implement a custom behavior. It is just a matter of implementing an action handler for the `error` action in the route.

It only takes a template to show an error message when loading a particular band does not work as it should. Let's create another template:

```shell
ember g template bands/band/error
```

We can display a similar panel, as we did for the loading template, with colors that indicate something slightly bad has happened:

Let’s talk about error subroutes and how to use them.

Error Subroutes

Course Overview

Getting Started with Ember

Templates and Data Bindings

Routing

Nested Routes

Components

Controllers

Building a Catalog

Talking to a Backend

Advanced Routing

Testing

Query Params

Loading and Error Substates

Helpers

Conclusion

Appendix

Error Subroutes

How error subroutes work