angularjs-directive

Code: <table> <tr> <ng-container ng-if="false"> // here ng-container not working <td> <ng-container ng-if="false">abc</ng-container>// here ng-container working fine </td> <td><ng-container ng-if="true">xyz</ng-container></td> </ng-container> </tr> </table> OutPut: xyz here expected output is no one cell was display but in between <tr> and <td> tags <ng-container ng-if="false"> are not working. If anyone idea about this problem please get solution. I analysis this issue in deep and i faced some situation like <ng-container ng-if=""> or <ng-container ng-show=""> or <ng-container ng-hide="">

I have an ng-repeat that loops over an array of objects. At each loop the value 'template' & 'values' is initialised. The following version works and uses ng-include to load the template but it happens to be very very slow: <tr class="tableRowsDocs" ng-repeat="dbo in rows track by $index"> <div ng-init="values = dbo.get4(attobj.key); key = attobj.key; template = attobj.template || getAttributeTemplate(dbo.clazz + attobj.key);"> <div class="content" ng-include="template"></div> </div> </td> </tr> The value for template and values is dynamic but it always holds the id of a template/script like:

I've created this angular directive that wraps a jQuery plugin datetimepicker. How can I get the default dates defined in the controller to display as the default date in the controls? http://jsfiddle.net/edwardtanguay/ef1o3c95/5 I've tried a number of variations with ngModel.$viewValue but can't get the yyyy-mm-dd text to simply display in the control. <div ng-controller="mainController"> <div class="form-group"> <div class='input-group date' timepicker ng-model="date1"> <input type='text' class="form-control" /> <span class="input-group-addon"><span class="glyphicon glyphicon-calendar"><

I have a directive (restrict A) that handles an event click, and calls a service based on a value. Directive: define(function () { 'use strict'; var myDirective = function ($rootScope, myFactory) { return { restrict: 'A', scope: { _myValue : '=value' }, link: function(scope, element, attrs) { element.bind('click', function() { if (scope._myValue === 'red') { myFactory.red(); } if (scope._myValue === 'green') { myFactory.green(); } if (scope._myValue === 'black') { myFactory.black(); } }); } }; }; return ['$rootScope', 'myFactory', myDirective]; }); Test: define(['angular-mocks'], function () {

I have a pattern wherein many item types are "editable". This means that I have lots of templates (one for each editable item type) that expect to have unique fields, but common functions (edit, save, cancel edit, delete, etc.). These common functions lead to lots of repetition on controllers: save , edit , cancel , etc., and very repetitive error-handling. One way I looked at of dealing with this was to have each controller "decorate" itself (using a service), but it got messy as well. I prefer a directive, say, 'editable': <form name="editGroup" editable> <div ng-show="editMode"> <!-- lots

http://embed.plnkr.co/oGlcQSOM2vFcDEKP7thV/ $injector.has('myMessageDirective') returns true, while $injector.has('myMessageComponent') does not Is anyone struggling with this or has a solution? My "fear" is that my components might not be found in future updates because of the directive check. Follow up question to: Check if an Angular directive exists At the end of the day, a component is registered as a directive, so 'Directive' suffix is indeed needed. Check 'has' method of $injector object: return { invoke: invoke, instantiate: instantiate, get: getService, annotate: createInjector.$