In my Ember template in my application, I have got a header tag, which should print the title of the current route. Does anyone know how I would accomplish this in EmberJS? Is there any way to set a variable once a route is accessed?
Route
Ember.Route.extend({
setupController: function(controller) {
controller.set('routeName', this.routeName);
}
});
Controller
Ember.Controller.extend({
routeName: null
});
Template
<header>{{routeName}}</header>
If you about application template, there is currentPath property in Application Controller (and in some other objects too, see details here: https://github.com/emberjs/ember.js/pull/12034
//application template
<header>{{currentPath}}</header>
There are a few ways.
First, an application controller has a property, currentPath. In this and this answers you may see examples of using it.
Also, you may use didTransition to determine when ember made a transition and update a title in some way.
And finally, if you want to change a document title (displayed in browser tab), there is an addon
Related
I have an Ember 2.11 application template with a few component placeholders at the moment (menu, breadcrumbs, related items) and an outlet which displays the main content which works fine. Now that I'm feeling more comfortable with the basics, I'm ready to try getting the breadcrumbs working.
I read about services, but I don't see that it is the right solution for breadcrumbs because it doesn't need to be persistent, it is based off the route. Although it is based off the route, I don't want to use the route literally as I want to use nice titles, and when viewing a specific item, the route doesn't accurately reflect what the breadcrumbs should show.
Since the breadcrumbs is based off the model that is being used for the display, I feel that I should be able to construct a breadcrumb object and then pass that into the component from the application template. I suppose this was the purpose of the controller back in the day. My thought was in the route to construct a breadcrumb object/property and return it with the model like RSVP and then I could access both in the template to pass the appropriate object to the appropriate component. But that seems wrong as the route should return an Ember data object, promise or Javascript array.
My current line of thinking is along these lines.
template/application.hbs
{{bread-crumbs crumbs=model.breadcrumbs}}
{{outlet}}
route/category/show
export default Ember.Route.extend({
model(params) {
let recipe = this.get('store').query('recipe', { category: params.category_id});
let crumbs = [{name: 'Category', link: 'category'},
{name: recipe.category.title, link: 'category.show', target: recipe.category.id}];
return {recipe: recipe, breadcrumbs: crumbs};
}
});
I'm not sure if this is the right way to approach this or if this will cause problems with async data fetching with Ember data. Something like this I would have to define on each route, but I don't have a lot of routes and seems to offer flexibility when I'm displaying a recipe (route is /recipe/recipe_id), but have the breadcrumbs show Home > Categories > Main Dishes > My Awesome Dish.
How would you approach the problem?
Updated 2017-02-10:
It appears that the model is not passed to the application template, only the route template. I'm not sure how to pass data 'down' to the application template.
You could probably create a breadcrumb like this by tracking the elements in a service, but I'd check out the ember-crumbly addon. It seems like it will meet your needs.
Remaining in your thinking line, if you want to pass your model as a variable of your controller in the route that you are accessing you need something like this:
export default Ember.Route.extend({
model(params){
let recipe = ...;
let crumbs = ...;
return {...};
},
setupController(controller, model){
this._super(controller, model);
controller.set('variable', model);
}
});
Having this, in your controller you can access to the crumbs like this:
this.get('variable');
And in then with an Ember.computed you can create a variable for display in your template.
Sorry for the minimize your code but I'm not in my computer.
Another approach is setting the crumbs variable at the init of the application controller, this set the variables defined in that controller global to the application, so you can modify them from other controllers and in the application controller lookup for that changes via didUpdateAttrs() or with didUpadteElement().
Hope this resolve your problem.
Greetings
I have a route defined like so:
Router.map(function() {
this.route('games', function() {
this.route('game', {path: '/:game_id'}, function() {});
});
});
When I visit path /games/1 I have to access the model data like so:
{{model.title}}
Reading the documentation, it seems that the controller would make the model data available without the model prefix so I thought I'd be able to do this:
{{title}}
But it doesn't work without model. I'm not creating the controller because I don't need to extend it for this particular route/template. Is accessing the model data via the model prefix accurate? Or am I possibly doing something else wrong?
The docs you are referring to are old, in the past (pre 1.13 iirc) the controller had a model proxy that would look up properties on the model if they weren't found on the controller.
This is no longer available since it was causing confusion in the community.
The new versions of the docs no longer reference {{title}} without model.
If you really want to use it without the model prefix you could resort to Ember.computed.alias though I would recommend sticking with model. as it is easier to read and identify as a model property vs controller property, especially since routable components are set to replace controllers in the near future (~2.6).
You can either use {{model.title}} or {{content.title}}. Earlier it possible to access properties directly using ObjectControllers but now as those are gone there is no other way.
[Edits]
There is one more way, you can extend setupController in route and set title on controller itself. That way you'll be able to directly use {{title}}.
setupController: function(controller, model) {
this._super(controller, model);
controller.set('title', model.get('title'));
}
Hope this helps.
In Ember, your model must be loaded by a route as described in the documentation here.
Assuming you are using ember-cli your route will look like :
export default Ember.Route.extend({
model: function() {
// Must return some data or promises
}
});
Model function can either return an array of data or a promises that will resolve to an array.
If you are using ember-data your function return will look like this :
return this.store.find('game', params.game_id);
You can also request directly to an API :
return Ember.$.getJSON('https://your-website.com/game/' + params.game_id);
I have a question regarding rendering a route into a component/outlet.
I would like to have a component that sits in the application template that acts like a modal/popover.
When rendering a route, I would like to render the template into the component, and when the content changes, run some logic in the component that opens/closes the popover.
I'm hoping someone can enlighten me on how I would go about doing this?
Currently I have a component in the application template, that has a named outlet inside of it (see below). I can render the route into that named outlet, but I can't figure out how to pick up the changes in the content when it changes. Clicking different links will change the content of that outlet.
Any thoughts? A better way to accomplish what I'm wanting to do?
app/templates/application.hbs
{{#primary-popover}}
{{outlet 'primary-popover'}}
{{/primary-popover}}
/app/profile/route.js
import Ember from 'ember';
export default Ember.Route.extend({
renderTemplate() {
this.render('profile', {
outlet: 'primary-popover'
});
}
});
I think the best way to solve your problem is to use liquid-fire http://ef4.github.io/liquid-fire/#/modals . It's recommended by ember core team library and also is well supported. It has nice modal component which can be triggered with link-to component or via this.transitionTo programmatically.
I am building an admin dashboard using ember. I want to create a reusable chart object of which I can have multiple instances throughout the application. The chart object should have a template consisting of some markup and a canvas element of which I need the id after insertion in the DOM in order to attach the actual chart (chart.js). I have tried several approaches, but I can not seem to figure out the right architecture to do this.
What would be the right architecture in ember to achieve the above?
Thanks!
Ember.Component is your friend
As #raulbrito already mentioned, the best way to go if you want reusable components in ember is indeed to use the new Ember.Component which is heavily based on the new w3 draft for web components and thus beeing future proof.
I've tried to make a simple example on how this could be implemented.
Given a simple route where the model hook returns some static data:
Index Route
App.IndexRoute = Ember.Route.extend({
model: function(){
return Ember.Object.create({
modelOne: data,
modelTwo: data2
});
}
});
data and data2 are simply static objects globally defined for simplicity (as you will see in the demo), but this could be also data coming from a backend or from fixtures etc.
Index template
In the template then we insert our chart component with the line {{line-chart data=model.modelOne}} and as you can see, we also set the data attribute to the index model model.modelOne or model.modelTwo:
<script type="text/x-handlebars" id="index">
<h2>Chart one</h2>
{{line-chart data=model.modelOne}}
<h2>Chart two</h2>
{{line-chart data=model.modelTwo}}
</script>
Component Template
Our component template looks fairly simple because it will render a simple canvas element, but it could be as complex as needed, on how to use Ember.Component please refer also to the docs:
<script type="text/x-handlebars" id="components/line-chart">
</script>
Component Subclass
App.LineChartComponent = Ember.Component.extend({
tagName: 'canvas',
attributeBindings: ['width', 'height'],
width: '480',
height: '360',
data: null,
didInsertElement: function() {
var ctx = this.get('element').getContext("2d");
var myNewChart = new Chart(ctx).Line(this.get('data'));
}
});
Note the naming is important here, Ember knows which subclass powers a component based on its name. For example, if you have a component called line-chart, you would create a subclass called App.LineChartComponent. If your component was called bar-chart-simple, the class name would be App.BarChartSimpleComponent and so on. Ember will look for a class with the camelized name of the component, followed by Component.
So, and since Ember.Component extends from Ember.View we can define all sorts of properties Ember.View supports like tagName. In our case we use canvas because this is what chart.js needs to work. As you can see we have also defined some attributeBindings to control the width and height of the canvas from inside ember. The component has also a data attribute (which could be called whatever you find appropriate) defined on which we later set our model data in the template returned from the IndexRoute model hook. And finally in your didInsertElement hook of our component we initialize the chart passing with this.get('data') the data object to new created Chart.js class.
var ctx = this.get('element').getContext("2d");
var myNewChart = new Chart(ctx).Line(this.get('data'));
And last but not least, please see here for a working example of the above explained.
Hope it helps.
Update in response to your last comment
I've tried to simulate a delay in the resolution of the model hook to mimic a response from a backend, as you can see the template rendering is waiting for the model promise to resolve first. Basically what I've done is to use Ember.run.later with a delay of 2000ms that resolves the promise once timed out:
App.IndexRoute = Ember.Route.extend({
model: function(){
return new Ember.RSVP.Promise(function(resolve) {
Ember.run.later(function() {
var m = Ember.Object.create({
modelOne: data,
modelTwo: data2
});
resolve(m);
}, 2000);
});
}
});
And just for fun I've also added a LoadingRoute to show a spinner while the promise resolution is waiting for data, the LoadingRoute is a less documented feature of ember, you can read more about it here: https://gist.github.com/machty/5647589 under How do I put up a (global) Loading Spinner during a transition w/ Promises?
Plase see here for a updated example: http://jsbin.com/odosoy/145/edit
Update in response to #SamSelikoff's comment
As for the above mentioned LoadingRoute #SamSelikoff pointed out that it's officially documented now: http://emberjs.com/guides/routing/defining-your-routes/#toc_initial-routes
I have some thoughts on this, so just throwing it out there, in case it helps you.
First of all, I would advise you to go and watch Sam Selikoff's presentation on using Ember with D3. All the info here: http://www.samselikoff.com/blog/2013/08/09/ember-d3-simple-dashboards/ . Also, don't miss the comments section on the blog post.
It is a great example on using Ember Views to wrap D3 objects, and can be a good reusable solution. The caveat here is that Ember Views require a backing controller that provides the data. Depending on where in the application you would want to reuse your charts, this might be inconvenience.
The alternative would be to use Ember Components. In that case, you just need to define the Component and associated handlebars template. The good thing about it is that it won't need any backing controller, therefore freeing you from a dependency, which might make it easier for you to add such a component in different places of your application. Without a concrete example, I think it's hard to reach a great conclusion, but maybe this will help you clarify things.
We are using one of the later versions of Ember (router V2), not the bleeding edge with the even newer Router V2.2 (Last commit: 668783a (2013-01-06 21:10:55 -0800))
In our solution we have several View components (Grid, autocomplete, search views etc.). Some of these components access the store, models etc. so they have a controller that handles that work. These views are used in several templates throughout our solution.
In the old version (pre2) we used those view components like this:
App.ConsoleView = Ember.View.extend({
templateName: 'console',
searchView: App.SearchView.extend(),
.....
})
And in the console template we used the common view like this
{{view view.searchView controllerBinding='App.searchController'}}
I have always felt that this approach is not the best way, and with the new version of Ember it has smacked us on our fingers :)
Now to the question: 'What is the recommended way to use a shared View in a template which needs a controller.'
In the newer versions of Ember the template expression
{{view view.searchView controllerBinding='App.searchController'}}
does not work because App.searchController is no longer instantiated at the App namespace.
I have thought of some choices but really don't like them.
I could connect the controller to the 'parent controller' through
the router, but then I would have to do this in every route where I
use a shared component, and that would be a lot.
I could fetch the controller through some hacky way and set it through the init function in the views init function.
Does someone have any recommendations on how to do this a good way? I cannot find any documentation on this, and have run out of googlejuize.
All responses will be appreciated!
I think I would try to use {{render "search"}}, it will lookup the searchController, then instantiate a SearchView and connect them.
Otherwise, I know there are currently discussion in order to beeing able to pass a controller class in the view helper. But not implemented yet.
Update: For now, I would perhaps use the second solution you propose, using https://github.com/emberjs/ember.js/blob/master/packages/ember-routing/lib/ext/controller.js#L33
App.ParentView = Ember.View.extend({
searchView = Ember.View.extend({
init: function(){
this._super();
this.set('controller', this.get('parentView.controller').controllerFor('search'))
}
})
})
Here I assume that all search view will share the same controller (and its underlying application state).