Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have updated your code so that it does what I think you want (at a minimum this works the way your old code does, but under rc3 as you wanted): <a href="http://plnkr.co/edit/nsq4BGAih3lfNmS2mLP7?p=preview" rel="nofollow">http://plnkr.co/edit/nsq4BGAih3lfNmS2mLP7?p=preview</a></p> <p>But I made quite a few changes and a significant architectural change so let me know if this moves away from the spirit of what you're trying to achieve.</p> <p>I think the gist of the issue was that your two directives (<code>generic</code> and <code>specific</code>) were tightly coupled around <code>contentVisible</code> which created a complex dependency that resulted in you having to very carefully manage invocation timing. My approach was to <strong>decouple the two directives</strong>- encapsulating <code>contentVisible</code> within <code>generic</code>. This allows <code>generic</code> and <code>specific</code> to instantiate fully independently. So you're not dependent on any invocation timing. And <strong>thus the directive priority change no longer has any impact on this code</strong>. So, one big win with the solution I propose is it should be robust against further changes by the Angular team.</p> <p>Specifically, I moved the template in to the same directive (<code>generic</code>) as the controller which manages <code>contentVisible</code> . This way the <strong>controller that changes <code>contentVisible</code> lives on the same scope as the template which uses it</strong>.</p> <p>Now <code>specific</code> just calls over to the <code>required:</code> <code>generic</code> controller to toggle visibility (effectively as a setter function).</p> <p>I also moved the <code>ng-class</code> assignment into the template in order to encapsulate that change within one place (the template) and so you don't need jquery or a <code>link:</code>/<code>compile:</code> on <code>generic</code>.</p>
    singulars
    1. This table or related slice is empty.
    1. POAngular 1.2.0-rc.3 Directive Priority Change Issue
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKayakDave
    1. USKayakDave
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUndeletion
    1. COYea, that moves away from what I was looking for. I have added another plunker example using better naming to hopefully convey my issue and what I am looking for.
      singulars
      1. PO
      1. USryanzec
    2. COThat does help. I think this is complicated because you're trying to get the directives to do more than DOM manipulation. You could decouple the directives from each other by moving your decision making up into mainCtrl (or you might want a new ngController that covers just the region of the page these directives live in). Then you can get back down to two directives, each with their own limited responsibilities and both talking to your controller (not directive controller, but an ngController).
      singulars
      1. PO
      1. USKayakDave
    3. COI am not sure if I am understanding you correctly. With the way I have things setup, to add expanding functionality I just need to add the expander and isolateScope directives to the html element and make sure they have an element with handle and content classes (only html changes). If I understand what you are saying, I would have to create a new ngController for each page (section) where I want this functionality which seems like a lot of duplication (unless I don't understand what you are saying).
      singulars
      1. PO
      1. USryanzec
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload