AngularJS: Why do custom directives default to being attribute-only? -

-

egghead.io has great explanation of directive restrictions in angularjs. custom directive can defined follows:

angular.module("app", []).directive("blah", function () {     return {         restrict: "a",         template: "blah directive. nothing see here."     }; });

this creates call attribute directive (due restrict: "a") purposes of asking question. angular's default restriction on custom directive, , directive can used like:

<div blah>   <!-- content of directive --> </div>

when want create custom directive, however, go element directive, like:

<blah>   <!-- content of directive --> </blah>

how former attribute directive better latter element directive , why chosen default?

this opinion, only:

there 3 possible ways define directive in html - attributes, elements , classes. classes lax , confusing, , best practice separate logic style. element directives strict - can have 1 "element" directive in dom element. makes them special right start.

an attribute seems best middle ground between these 2 extremes - clear, allows multiple directives in element (if following egghead's videos, superhero example on "directive directive communication" shows kind of "directive hierarchy", elements superseding attributes. also, , important of times (i program intranet apps, me isn't) attributes allow angularjs templates valid html.

edit - 2 cents be doesn't matter - in real scenario, bad idea trust "default" configuration of primary restrict option - setting explicitly makes clear, no doubt directives (especially working in team projects, anytime, really)


Comments

Post a Comment

Popular posts from this blog

java - Jmockit String final length method mocking Issue -

-
using jmockit 1.2 jar, trying mock string's length method getting unexpected invocation exception: failed: test java.lang.illegalstateexception: missing invocation mocked type @ point; please make sure such invocations appear after declaration of suitable mock field or parameter @ stringdemo.testa$1.<init>(testa.java:17) @ stringdemo.testa.test(testa.java:13) i using testng: @test public void test() throws exception { new expectations() { @mocked("length") string astring; { astring.length(); result = 2; } }; system.out.println(a.showa("test")); } } actual class a: public class { public static int showa(string str){ int a= str.length(); return a; } } this wrong way of recording expected results. shouldn't mock , record string's length() method, record showa() instead. here solution @suppresswarnings("unused...
Read more

What is the difference between data design and data model(ERD) -

-
i have google question , find answer in day. know, data design many many table have list column,and mark pk , fk. why er-diagram have find this? data design process of designing database. main output of data design detailed logical data model of database. some people data design includes of needed logical , physical design choices , physical storage parameters needed generate design in data definition language. technically, database analysis, database analysts (dbas) trained do. while person can both data design , database analysis, these 2 different tasks. data design models data. database analysis takes model , applies 1 or more database engines (relational, hierarchical, nosql). a logical data model 1 of main outputs of data design. data model represented entity relationship diagram, or er diagram.
Read more

ios - Can NSManagedObject conform to NSCoding -

-
i need transfer single object across device. right converting nsmanagedobject dictionary , archiving , sending nsdata. upon receiving unarchiving it. transfer nsmanagedobject archiving , unarchiving instead of creating intermediate data object. @interface test : nsmanagedobject<nscoding> @property (nonatomic, retain) nsstring * title; @end @implementation test @dynamic title; - (id)initwithcoder:(nscoder *)coder { self = [super init]; if (self) { self.title = [coder decodeobjectforkey:@"title"]; //<crash } return self; } - (void)encodewithcoder:(nscoder *)coder { [coder encodeobject:self.title forkey:@"title"]; } @end nsdata *archivedobjects = [nskeyedarchiver archiveddatawithrootobject:testobj]; nsdata *objectsdata = archivedobjects; if ([objectsdata length] > 0) { nsarray *objects = [nskeyedunarchiver unarchiveobjectwithdata:objectsdata]; } the problem above code is. crashes @ self.title in initwithcoder sa...
Read more