Haven't decided if I am going to submit code to it yet
👍 - Unlocked & Done 😊 - Locked & Done 🔒 - Locked & Not Done [] - Not yet Done
var data = [ | |
{ a: 4, b: 12, c: "elderberry" }, | |
{ a: 2, b: 10, c: "cherry", d: 4 }, | |
{ a: 4, b: 12, c: "durian" }, | |
{ a: 2, b: 10, c: "cherry", }, | |
{ a: 3, b: 12, c: "durian" }, | |
{ a: 1, b: 10, c: "apple", }, | |
{ a: 1, b: 11, c: "apple", }, | |
{ a: 1, b: 11, c: "banana", }, | |
{ a: 2, b: 10, c: "banana", }, |
# Name of the resource we're selectively copying | |
GOOGLESERVICE_INFO_PLIST=GoogleService-Info.plist | |
# Get references to dev and prod versions of the GoogleService-Info.plist | |
# NOTE: These should only live on the file system and should NOT be part of the target (since we'll be adding them to the target manually) | |
GOOGLESERVICE_INFO_DEV=${PROJECT_DIR}/${TARGET_NAME}/Firebase/Dev/${GOOGLESERVICE_INFO_PLIST} | |
GOOGLESERVICE_INFO_PROD=${PROJECT_DIR}/${TARGET_NAME}/Firebase/Prod/${GOOGLESERVICE_INFO_PLIST} | |
# Make sure the dev version of GoogleService-Info.plist exists | |
echo "Looking for ${GOOGLESERVICE_INFO_PLIST} in ${GOOGLESERVICE_INFO_DEV}" |
We prefer to have audit logging in our services that leverage databases. It gives us clarity into sources of where ACL issues might originate as well as gives us a general timeline of activity in our application.
Audit logging is tedious to set up so this gist contains our latest iteration of audit logging support for a sequelize based service.
Quick writeup on how I do Node/npm on Windows.
Inspired by dannyfritz/commit-message-emoji
See also gitmoji.
Commit type | Emoji |
---|---|
Initial commit | 🎉 :tada: |
Version tag | 🔖 :bookmark: |
New feature | ✨ :sparkles: |
Bugfix | 🐛 :bug: |
function (doc, req) { | |
var findTheChanges = function (prevK, obj) { | |
var arr = []; | |
for (var key in obj) { | |
var prevKey = prevK || ''; | |
if (obj.hasOwnProperty(key)) { | |
var value = obj[key]; | |
// If its an Object dig deeper. | |
if (value !== null && | |
typeof value === 'object' && |
These are the Kickstarter Engineering and Data role definitions for both teams.
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
, elem.offsetTop
, elem.offsetWidth
, elem.offsetHeight
, elem.offsetParent