StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Eureka! I figured it out! The below answer is in the form of a library I'm writing but it should be relatively easy to follow.</p> <p>As it turns out, the best course of action (as far as I can tell) is to first using a separate function, build an object from the target object containing all the property paths:</p> <pre><code>/** * Returns an object containing all of the property paths of an object. Each * property path is referenced by the property name. * @param {object} The object to target * @return {object} Object containing paths ELSE undefined */ paths: function( obj, path, lastKey, nextKey ) { var o, key, path = path ? path : {}, lastKey = lastKey ? lastKey : "", nextKey = nextKey ? nextKey : ""; for ( o in obj ) { // Push path onto stack path[o] = (nextKey + "." + lastKey + "." + o).replace(/^[.]+/g, ""); // Pass updated "nextKey" along with next recurse key = nextKey + "." + lastKey; // Call again on all nested objects if ( (lib).isPlainObject(obj[o]) ) { (lib).paths(obj[o], path, o, key); } } return (lib).len(path) ? path : undefined; }, </code></pre> <p>Then we use the resolve method as a "wrapper" to the paths method, returning the targeted property key's namespace.</p> <pre><code>resolve: function( obj, key ) { return (lib).paths(obj)[key]; }, </code></pre> <p>Using the object I posted originally above:</p> <pre><code>var res = o.resolve(obj, "A_2_b_1"); // Returns "A.A_2.A_2_b.A_2_b_1" </code></pre> <p>Just for reference, the <code>paths</code> method returns an object that looks something like this:</p> <pre><code>// { // A: [...] // A_1: [...] // A_2: [...] // A_2_a: [...] // A_2_b: [...] // A_2_b_1: [ // 0: "A_2_b_1" // 1: "A.A_2.A_2_b.A_2_b_1" // ] // A_2_b_2: [...] // A_2_c: [...] // A_3: [...] // B: [...] // ... // } </code></pre> <p>Where each property maps to its path in the object.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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