StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20205329
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-11-25T23:06:02.363
FavoriteCount
0
LastActivityDate
2013-11-25T23:06:02.363
LastEditDate
LastEditorUserId
0
OwnerUserId
202913
ParentId
20131797
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
<p>Mixing isolated scope with ngModel is a documented issue, see the <strong>Isolated Scope Pitfall</strong> section in the <a href="http://docs.angularjs.org/api/ng.directive%3angModel.NgModelController">documentation</a>: </p> <blockquote> <p>Isolated Scope Pitfall Note that if you have a directive with an isolated scope, you cannot require ngModel since the model value will be looked up on the isolated scope rather than the outer scope. When the directive updates the model value, calling ngModel.$setViewValue() the property on the outer scope will not be updated. However you can get around this by using $parent.</p> </blockquote> <p>Using this knowledge and some freaky scope experiments I've come with two options that does what you want to do:</p> <p>(1) See this <a href="http://jsfiddle.net/W8cCm/4/">fiddle</a> It makes use of the $parent method as described above.</p> <pre><code><div ng-controller="MyCtrl"> <div> <input ng-form type="text" ng-model="$parent.search" append-me terms="myTerms"> </div> {{search}} </div> myApp.directive('appendMe', ['$compile', function($compile) { return { restrict: 'A', scope: {terms: '='}, link: function(scope, element, attributes) { // linking function console.log(scope.terms); var template = '<p>test</p>' + '<ul><li ng-repeat="term in terms">{{term}}</li></ul>' + '<p>hm…</p>' element.after($compile(template)(scope)); } } }]); </code></pre> <p>(2) See this <a href="http://jsfiddle.net/W8cCm/3/">fiddle</a> It does not use $parent, instead it uses the isolated scope to publish the search model as configured via ngModel.</p> <pre><code><div ng-controller="MyCtrl"> <div> <input ng-form type="text" ng-model="search" append-me terms="myTerms"> </div> {{search}} </div> myApp.directive('appendMe', ['$compile', function($compile) { return { restrict: 'A', scope: {terms: '=', search: '=ngModel'}, link: function(scope, element, attributes) { // linking function console.log(scope.terms); var template = '<p>test</p>' + '<ul><li ng-repeat="term in terms">{{term}}</li></ul>' + '<p>hm…</p>' element.after($compile(template)(scope)); } } }]); </code></pre> <p>Both options seem to work just fine.</p>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAngular directives: mixing attribute data and ngModel
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBeyers
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
2. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
3. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
CommentsPostId
1. COI think option #2 is the way to go. People seem to forget that they can just read other directive's attributes.
  singulars
  PostPostId
  PO
  UserUserId
  USdtabuenc

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.