parent
abc1580fa9
commit
3869818d8f
|
@ -52,7 +52,7 @@ CSS Selectors can be combined:
|
|||
|
||||
## Directives
|
||||
|
||||
The simplest kind of directive is a decorator. Directives are usefull for encapsulating behavior.
|
||||
The simplest kind of directive is a decorator. Directives are useful for encapsulating behavior.
|
||||
|
||||
* Multiple decorators can be placed on a single element.
|
||||
* Directives do not introduce new evaluation context.
|
||||
|
@ -260,7 +260,7 @@ Injecting other directives into directives follows a similar mechanism as inject
|
|||
|
||||
There are five kinds of visibilities:
|
||||
|
||||
* (no annotation): Inject dependant directives only if they are on the current element.
|
||||
* (no annotation): Inject dependent directives only if they are on the current element.
|
||||
* `@ancestor`: Inject a directive if it is at any element above the current element.
|
||||
* `@parent`: Inject a directive which is a direct parent of the current element.
|
||||
* `@child`: Inject a list of direct children which match a given type. (Used with `Query`)
|
||||
|
@ -325,7 +325,7 @@ Assume the following DOM structure for `my_app.html`:
|
|||
|
||||
#### Shadow DOM effects on Directive DI
|
||||
|
||||
Shadow DOM provides an encapsulation for components, so as a general rule it does not allow directive injections to cross the shadow DOM boundaries. To remedy this, declaritively specify the required component as an injectable.
|
||||
Shadow DOM provides an encapsulation for components, so as a general rule it does not allow directive injections to cross the shadow DOM boundaries. To remedy this, declaratively specify the required component as an injectable.
|
||||
|
||||
```
|
||||
@Component({
|
||||
|
|
|
@ -4,7 +4,7 @@ Benchpress is a framework for e2e performance tests.
|
|||
|
||||
# Why?
|
||||
|
||||
There are so called "micro benchmarks" that esentially use a stop watch in the browser to measure time
|
||||
There are so called "micro benchmarks" that essentially use a stop watch in the browser to measure time
|
||||
(e.g. via `performance.now()`). This approach is limited to time, and in some cases memory
|
||||
(Chrome with special flags), as metric. It does not allow to measure:
|
||||
|
||||
|
@ -80,7 +80,7 @@ index.html:
|
|||
var container = document.getElementById('container');
|
||||
var complexHtmlString = '...'; // TODO
|
||||
|
||||
function reset() { cotainer.innerHTML = ''; }
|
||||
function reset() { container.innerHTML = ''; }
|
||||
|
||||
function fill() {
|
||||
container.innerHTML = complexHtmlString;
|
||||
|
|
|
@ -28,7 +28,7 @@ assert(value).is(...)
|
|||
|
||||
// Custom type assert:
|
||||
// - i have a custom type
|
||||
// - adding an assert methos
|
||||
// - adding an assert methods
|
||||
assert.define(MyUser, function(value) {
|
||||
assert(value).is(Type, Type2); // or
|
||||
assert(value, 'name').is(assert.string);
|
||||
|
|
Loading…
Reference in New Issue