dinana

User.find(id).populate('preferences').exec(function (err, user) {
    if(err) {
        sails.log.error("ERR:", err);
    }
    sails.services['util'].populateDeep('user', user[0], 'preferences.nestedPreferences', function (err, newUser) {
        if (err) {
            sails.log.error("ERR:", err);
        }
        console.log(newUser);
    });

maephisto

var isoCountries = {
    'AF' : 'Afghanistan',
    'AX' : 'Aland Islands',
    'AL' : 'Albania',
    'DZ' : 'Algeria',
    'AS' : 'American Samoa',
    'AD' : 'Andorra',
    'AO' : 'Angola',
    'AI' : 'Anguilla',
    'AQ' : 'Antarctica',

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

danpaluska

from gdata.youtube import YouTubeVideoEntry
from gdata.youtube.service import YouTubeService
import gdata
from gdata.service import BadAuthentication, CaptchaRequired


from optparse import OptionParser
import sys
import time
import os