Here's is a quick-and-dirty summary of all the important things (from the point of view of SONY and PSNOW) that happened at Ember Conf 2018.
- nucleartide's notes https://github.com/nucleartide/emberconf-2018
Here's is a quick-and-dirty summary of all the important things (from the point of view of SONY and PSNOW) that happened at Ember Conf 2018.
@dgeb is apparently working on a large git-inspired approach to organization data and io in javascript, he calls the project [orbit.js|http://orbitjs.com/] and this project meets its first user case in ember-data.
Here's how this could be applicable to us:
Marie Chatfield went over a deep dive on DOM events in Ember. Here's the big takeaway:
Don't attach DOM-element listeners:
and instead use Ember ones:
Godfrey Chan's Prying Open the Black Box
Ember Debug Library
Ember has a debug library with methods like
assert
anddebug
that will allow us to make assertions within our code and log to the console, respectively. They are removed before the app is shipped to production.import { assert, debug } from '@ember/debug';
You can write assertions as simple as the example below:
Debug statements will be written as any
console.log
statement using the debug syntax.Handlebars Debugger
You can also use
{{debugger}}
statements in handlebars to toggle elements at certain rendering points.When using the debugger helper you will have access to a
get
function. This function retrieves values available in the context of the template. For example, if you're wondering why a value{{foo}}
isn't rendering as expected within a template, you could place a {{debugger}} statement and, when the debugger; breakpoint is hit, you can attempt to retrieve this value: