Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>After writing a lot of directives, I've decided to use less <code>isolated</code> scope. Even though it is cool and you encapsulate the data and be sure not to leak data to the parent scope, it severely limits the amount of directives you can use together. So, </p> <p>If the directive you're going to write is going to behave <strong>entirely</strong> on its own and you are not going to share it with other directives, go for <em>isolated scope</em>. (like a component you can just plug it in, with not much customization for the end developer) (it gets very trickier when you try to write sub-elements which have directives within)</p> <p>If the directive you're going to write is going to <em>just</em> make dom manipulations which has needs no internal state of scope, or explicit scope alterations (mostly very simple things); go for <em>no new scope</em>. (such as <code>ngShow</code>, <code>ngMouseHover</code>, <code>ngClick</code>, <code>ngRepeat</code>)</p> <p>If the directive you're going to write needs to change some elements in parent scope, but also needs to handle some internal state, go for <em>new child scope</em>. (such as <code>ngController</code>)</p> <p>Be sure to check out the source code for directives: <a href="https://github.com/angular/angular.js/tree/master/src/ng/directive">https://github.com/angular/angular.js/tree/master/src/ng/directive</a><br> It greatly helps on how to think about them</p>
    singulars
    1. This table or related slice is empty.
    1. POWhen writing a directive in AngularJS, how do I decide if I need no new scope, a new child scope, or a new isolated scope?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USUmur Kontacı
    1. USUmur Kontacı
    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. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf several components needs to communicate with each other, they can have isolated scope and use `require`, so keeping your directives still decoupled. So how it limits possibilities? It even more makes directives more specific (so declare what you're depend on). So I would leave only one rule: if your directive has state or needs some data from scope where it is used - use isolated scope. Otherwise do not use scope. And about "child scopes" - I've also wrote quite a lot directives and never needed this feature. If "needs to change some elements in parent scope" - use bindings.
      singulars
      1. PO
      1. USValentyn Shybanov
    2. COAnd also about "needs to change some elements in parent scope" - if you modify something in child scope changes are not populated to parent scope (unless you use dirty `$parent` hack). So actually "child scopes" for directives is something that looks like should be used quite rear - like `ngRepeat` that creates new child scopes for each item to repeat (but it also creates it using `scope.$new();` and not `scope: true`.
      singulars
      1. PO
      1. USValentyn Shybanov
    3. COYou cannot ask for multiple isolated scopes within the same element, you cannot access to the functions in the parent scope, unless you bind them explicitly. (Good luck using `ngClick` etc.) Requiring creates a kind of decoupling I agree, but you still need to aware of the parent directive. Unless it is like a *component*, I'm against going for isolation. Directives (at least, most of them) are meant to be highly reusable and isolation breaks this.
      singulars
      1. PO
      1. USUmur Kontacı
 

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