Page History
...
A handler call to the server does get a promise back (http://docs.angularjs.org/api/ng.$q) where the webcomponent could register a callback on so that an event that executes on the server can return a value to the webcomponents call.
| Info | ||
|---|---|---|
| ||
A WebComponent directive should expect that the attributes it receives (except for svyApi) can completely change. For example when the record shown by a component changes the svyModel it gets will change by reference. So be careful about caching model contents or accessing some model content just for example in the link method of the directive (which will not be called again when just displayed record changes). If you write any repeater components (such as custom portals/table views/list views) you should make sure you don't change the svyApi that you give to the same child WebComponent directive (and which was populated by that directive initially) when the record that it displays changes. |
Overview
Content Tools
Activity