In the template we are defining the cells for every article row and reading the value from the “passed- in” property article, notice also that we are calling the action “saveArticle” and not “save”.
We are also using the emberx-select addon, which includes a select component based on the native html select element, in the value attribute we are binding the selection to the article’s state and then for every possible state we are rendering an option element.
grammar edited for legibility:
In the template we are defining the cells for every article row and reading the value from the “passed- in” property article. Notice that we are calling the action “saveArticle” not “save”.
We are using the emberx-select addon, which includes a select component based on the native html select element. In the value attribute we are binding the selection to the article’s state and then for every possible state we are rendering an option element.
edition: 2015-07-20 format: pdf page: 70
original text:
In the template we are defining the cells for every article row and reading the value from the “passed- in” property article, notice also that we are calling the action “saveArticle” and not “save”. We are also using the emberx-select addon, which includes a select component based on the native html select element, in the value attribute we are binding the selection to the article’s state and then for every possible state we are rendering an option element.
grammar edited for legibility:
In the template we are defining the cells for every article row and reading the value from the “passed- in” property article. Notice that we are calling the action “saveArticle” not “save”. We are using the emberx-select addon, which includes a select component based on the native html select element. In the value attribute we are binding the selection to the article’s state and then for every possible state we are rendering an option element.