Databases
StackOverflow2013
Postsdbo
POAngularJS DOM / document selections without jQuery
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAngularJS DOM / document selections without jQuery
    primarykey
    data
    text
    <p>AngularJS doesn't have a built in DOM selection engine yet provides utility methods that handle a portion of what jQuery would provide for a typical application.</p> <p>However, DOM selection is still king and I'm trying to keep jQuery out of my application for the sole purpose of DOM selections.</p> <p>Angular provides a $document service as an injectable. I find this to be cumbersome. For example, to achieve native DOM selections using $document you would need to inject $document into all directives desired and call querySelectorAll, then extend it with Angular:</p> <pre><code>angular.element( $document[0].querySelectorAll('#element') ) </code></pre> <p>This is silly. </p> <p>In there interim I've provided myself a global helper, but it doesn't use Angular's wrapped $document...</p> <pre><code> // Create a shortcut to querySelectorAll window.query = function(selector) { return document.querySelectorAll( selector ) } // For use inside a directive like so... angular.element( query('#element') ) </code></pre> <p>AngularJS is ALLERGIC to globals and wraps globals for protection and testability. Is there a clean way I can leverage querySelectAll without passing $document into every directive? Can I extend angular.element in the same fashion jQuery does but utilize querySelectorAll?</p> <p><strong>Edit:</strong></p> <p>I also want to note the original JQLite library supports basic selectors <a href="https://code.google.com/p/jqlite/wiki/UsingJQLite#Supported_Selectors" rel="nofollow">https://code.google.com/p/jqlite/wiki/UsingJQLite#Supported_Selectors</a>.</p> <p>The AngularJS implementation however does not support selectors nor appears to mention this feature omission - <a href="http://docs.angularjs.org/api/angular.element" rel="nofollow">http://docs.angularjs.org/api/angular.element</a></p> <p>Instead AngularJS does:</p> <pre><code>throw Error('selectors not implemented'); </code></pre> <p>^ when the item passed to angular.element is a string which does not start with '&lt;'.</p> <p>It'd be nice if that was:</p> <pre><code>return document.querySelectorAll( element ) </code></pre> <p>...with some basic error prevention logic.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBradGreens
    1. USBradGreens
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POAngularJS DOM / document selections without jQuery
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POAngularJS DOM / document selections without jQuery
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHave you thought about using something like [Sizzle](http://sizzlejs.com/) instead of full jQuery? (jQuery runs on this internally.)
      singulars
      1. POAngularJS DOM / document selections without jQuery
      1. USjedd.ahyoung
    2. COI have, and it might be the way to go until Angular adopts a selection pattern. You'll see I've updated the post indicating I wish it'd just return a document.querySelectorAll attempt at the point of the exception. I mean, why not? There's no bloat being added here.
      singulars
      1. POAngularJS DOM / document selections without jQuery
      1. USBradGreens
    3. COI should also note that when the Angular team recommends document.querySelectorAll in these cases, they are defecting from their wrapped global patterns which they advocate in places like here - http://docs.angularjs.org/api/ng.$window.
      singulars
      1. POAngularJS DOM / document selections without jQuery
      1. USBradGreens
 

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