首页 \ 问答 \ Angular：指令内的变量模板(Angular: Variable template inside directive)

Angular：指令内的变量模板(Angular: Variable template inside directive)

 在我的Angular模板中，我使用了一个定语指令，如下所示：  
 HTML：  
<div id="my-template-one" my-template-directive></div>
 
 JS：  
// ...
.directive('myTemplateDirective', ['myconfig', function (myconfig) {
        return {
            templateUrl: myconfig.TEMPLATE_PATH + 'my-template-one.html',
            controller: function ($scope, $rootScope) {
                // code
            },
            controllerAs: 'dir'
        }
    }]);
 
 为了在另一个页面上包含另一个模板my-template-two.html ，我想使用相同的指令。 我不想复制指令。 如何将模板作为变量传递？  
 另一页上的HTML：  
<div id="my-template-two" my-template-directive></div>
 
 我的目标是以某种方式告诉我的指令在调用此HTML时呈现my-template-two.html 。 

In my Angular template I use an attributive directive as follows: 
HTML: 
<div id="my-template-one" my-template-directive></div>
 
JS: 
// ...
.directive('myTemplateDirective', ['myconfig', function (myconfig) {
        return {
            templateUrl: myconfig.TEMPLATE_PATH + 'my-template-one.html',
            controller: function ($scope, $rootScope) {
                // code
            },
            controllerAs: 'dir'
        }
    }]);
 
For including another template, my-template-two.html, on another page, I would like to use the same directive. I do not want to duplicate the directive. How can I pass the template as an variable? 
HTML on another page: 
<div id="my-template-two" my-template-directive></div>
 
My goal is that somehow I can tell my directive to render my-template-two.html when this HTML is called.

原文：https://stackoverflow.com/questions/39249847

更新时间：2023-07-26 19:07

最满意答案

 “错误”并不意味着错误，它只是意味着返回的对象是一个“幽灵”而没有读入其属性。为关系的另一方获取错误是正常的，因为你没有设置的提取通过其关系从一个不受控制的对象创建级联。  
 当您访问故障的属性时，它将作为一个功能齐全的对象出现故障。  
 编辑：  
 来自评论：  
 
  问题是我通过NSLog请求这种关系，但我仍然无法得到关系实体。  
 
 不你不是。 您只需要自己请求Items实体然后记录它们。 他们按照预期为他们的关系返回错误。 只有当你问每一个关系另一边的实际对象时，你才能保证看到一个对象而不是一个错误。  
 这就是你需要强制关系中对象的错误：  
NSLog(@"itemObject.Item_to_item_comments: %@", [mutableItemsFetchResults objectAtIndex:indexPath.row].Item_to_item_comments.someAttribute]);
 
 你还有一个问题就是你正在比较两个单独提取的结果。 这个：  
NSLog(@"Results: %@", [mutableItemsFetchResults description]);
mutableItemsFetchResults = [[managedObjectContext executeFetchRequest:request error:nil] mutableCopy];
 
 ...在mutableItemsFetchResults 之前记录mutableItemsFetchResults 。 下一个NSLog（可能）在获取后记录结果。 这意味着您可能会在两种不同的故障状态下查看两组不同的对象。  
 您可能也有问题，因为mutableItemsFetchResults显然是一个属性，但您没有使用self.mutableItemsFetchResults表示法来确保它被正确保留。 另外，我认为你不需要mutableCopy 。 

A "fault" doesn't mean an error, it just means that the object returned is a "ghost" without its attributes read in. It's normal to get faults for the other side of relationship because you don't what a fetch to set off an uncontrolled cascade of object creation via its relationships.  
When you access an attribute of the fault, it will be faulted in as a fully functional object. 
Edit: 
From comment: 
 
 The problem is that I am requesting such relationship through NSLog, but I still can't get the relationship entities. 
 
No you're not. Your just requesting the Items entities themselves and then logging them. They are returning faults for their relationships as expected. Only if you ask each for the actual object on the other side of the relationship are you guaranteed to see an object instead of a fault.  
This is what you need to force the faulting-in of the objects in the relationship: 
NSLog(@"itemObject.Item_to_item_comments: %@", [mutableItemsFetchResults objectAtIndex:indexPath.row].Item_to_item_comments.someAttribute]);
 
You're other problem is that you are comparing the results of two seperate fetches. This: 
NSLog(@"Results: %@", [mutableItemsFetchResults description]);
mutableItemsFetchResults = [[managedObjectContext executeFetchRequest:request error:nil] mutableCopy];
 
... logs the mutableItemsFetchResults before the fetch occurs. The next NSLog (presumably) logs the results after the fetch. This means you're looking at possibly two different sets of objects in two different fault states.  
You may also have a problem because mutableItemsFetchResults is apparently a property but you're not using the self.mutableItemsFetchResults notation to make sure it is properly retained. Also, I don't think you need themutableCopy.

Angular：指令内的变量模板(Angular: Variable template inside directive)

最满意答案

相关问答

iPhone SDK的核心数据：获取所有实体与零关系？(iPhone SDK Core Data: Fetch all entities with a nil relationship?)[2022-10-05]

iPhone上的JSON和核心数据(JSON and Core Data on the iPhone)[2023-08-02]

iphone / ios - 核心数据关系概念(iphone/ios - core data relationship concept)[2022-11-04]

Core Data与关系中的参数的关系(Core Data relationship with parameter in relationship)[2022-10-30]

核心数据多对多关系更新导致故障(Core Data Many-to-Many relationship update causes fault)[2023-05-11]

Core Data for iPhone入门？(Getting started in Core Data for iPhone?)[2023-01-17]

iPhone：在Core Data中存储视频和音频？(iPhone: Storing video and audio in Core Data?)[2021-06-17]

iPhone Core Data关系错误(iPhone Core Data relationship fault)[2023-10-02]

iPhone - 核心数据NSSet关系(iPhone - core data NSSet relationship)[2022-05-01]

核心数据可以重新排除内存中的图像吗？(Core Data can I re-fault images out of memory?)[2022-10-22]

相关文章

最新问答