Stephen Belcher sycobuny

So, in the IIFE section of the angular styleguide, it suggests using function expressions to encapsulate angular component definitions inside of a function expression in order to keep the logic easy to understand while also keeping the global namespace clear.

And, later in the document, it has a more complete example including putting binding members of a controller at the top of a function defining a component. It shows that, inside of this component's function, more functions are declared.

This query is meant to serve as a proof-of-concept for parsing sleep data off of the fitbit API, which returns you a start date, and then a series of times. Given that these data are polled every minute, you can safely assume that, when you cross a date boundary, the next measurement of time will be "smaller" than the last, and we could just break it into two days.

However, in an extreme edge case where either the fitbit is reporting wrong, or someone really is sleeping for more than 24 hours,

	myApp.factory('queryStringFactory', [function() {
	return function(obj) {
	var params = []

	for (var key in obj) {
	params.push(
	encodeURIComponent(key) + '=' + encodeURIComponent(obj[key])
	)
	}

	// describe the constants as angular constants, namespaced to the controller that uses them
	(function(angular, undefined) {
	angular.module('myapp').constant('MyCtrl.API_ENDPOINT', 'https://myserver.com/data.json')
	})(angular)

	WITH
	thing_id(i) AS (VALUES (123)),
	new_tag_list(t) as (
	VALUES ('t1', 't2')
	),
	inserted_tags(tagid, thingid) AS (
	INSERT INTO tags_things
	(tag_id, thing_id)
	SELECT nt.id,
	(SELECT id FROM thing_id LIMIT 1)

	Old string: Here's a string with a couple ' in it
	New String: Here\'s a string with a couple \' in it