Michael Villander villander

Here is a high level overview for what you need to do to get most of an Android environment setup and maintained.

Prerequisites (for Homebrew at a minimum, lots of other tools need these too):

XCode is installed (via the App Store)
XCode command line tools are installed (xcode-select --install will prompt up a dialog)
Java

Install Homebrew:

ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"

Service Worker - offline support for the web

Progressive apps - high-res icon, splash screen, no URL bar, etc.

Progressive Web Apps: Escaping Tabs Without Losing Our Soul

I've developed a useful feature in KeystoneJS that lets you populate a relationship from either side, while only storing the data on one side, and am looking for feedback on whether it is something that could / should be brought back into mongoose itself. (It might be possible to add as a separate package but I suspect there'd be too much rewriting of mongoose internals for that to be a good idea).

I've added this as an issue in mongoose for consideration: #1888 but am leaving this gist in place because the examples are easier to read.

I've used Posts and Categories as a basic, contrived example to demonstrate what I'm talking about here; in reality you'd rarely load all the posts for a category but there are other real world cases where it's less unreasonable you'd want to do this, and Posts + Categories is an easy way to demo it.

The problem

The built-in population feature is really useful; not just for

	import Ember from 'ember';

	const { computed: { alias }, observer } = Ember

	export default Ember.Component.extend({
	routing: Ember.inject.service('-routing'),
	params: alias('routing.router.currentState.routerJsState.fullQueryParams')
	})

	import Ember from 'ember';

	export default Ember.Controller.extend({
	appName:'Nested Routes - Loading'
	});

	import Ember from 'ember';

	const DATA_URL = 'https://api.github.com/orgs/emberjs/repo';

	export default Ember.Route.extend({

	// Values returned from async function are Promises
	model: async function() {
	// Get the data, AND WAIT FOR IT TO RETURN (type: Object)
	var data = await $.getJSON(DATA_URL);

	import Ember from 'ember';
	import moment from 'moment';

	export default Ember.Component.extend({

	init(){
	this._super(...arguments);
	console.log(`${this.get('day')}`);
	isActive: true;
	},

	import Ember from 'ember';
	import { makeTestPromise } from '../utils/test-foo';

	const TestFoo = Ember.Object.extend(Ember.PromiseProxyMixin, {
	init() {
	// By default a PromiseProxy will rethrow a
	// rejected promise causing it to be left
	// unhandled. Since by the nature of this use
	// pattern it is handled (see template) we add
	// a no-op to the end of the chain and the

	didRecieveAttrs(attrs) {
	if (attrs.newAttrs.dimensions.value !== attrs.oldAttrs.dimensions.value) {
	chart.redraw();
	}
	}

	var fb = new DSFirebaseAdapter({
	basePath: 'https://my-app.firebase.io'
	});

	var ls = new DSLocalStorageAdapter();

	var store = new JSData.DS({
	// try firebase first, otherwise try offline data
	fallbackAdapters: ['fb', 'ls'],
	// After creating an item, sync it to localStorage