Replace the variables below in the script
YOURBASEID
: your Airtable base ID starting with 'app...'YOURCOOKIESFORAIRTABLEDOMAIN
your browser cookie for airtable.com domain
const fda = ( fields ) => { | |
let data = [] | |
for(const f of fields ){ | |
data.push(fd(f)) | |
} | |
return data | |
} | |
const fd = ( field ) => { | |
let data = { |
Mute these words in your settings here: https://twitter.com/settings/muted_keywords | |
ActivityTweet | |
generic_activity_highlights | |
generic_activity_momentsbreaking | |
RankedOrganicTweet | |
suggest_activity | |
suggest_activity_feed | |
suggest_activity_highlights | |
suggest_activity_tweet |
function removeFirstConnection () { | |
$('[type=ellipsis-horizontal-icon]').first().click() | |
setTimeout(() => { | |
$('.js-mn-connection-card__dropdown-delete-btn > button').click() | |
setTimeout(() => { | |
$('[data-control-name="confirm_removed"]').click() | |
}, 250) | |
}, 250) | |
} |
This is a simplified, but fairly thorough, set of scripts and configuration to enable Heroku Release Phase for Rails apps.
Further, this particular set up plays nicely with Heroku Review Apps in that the release
phase script will:
bin/rails db:version
) is 0
.For a "normal" app that usually means it will run the DB migrations.
-----BEGIN PGP PUBLIC KEY BLOCK----- | |
Version: GnuPG v1 | |
mQINBFMgUU0BEAC50m+8R2DVAG6hP9FurOBez+6ebhFWwzLqU5cTmS1jiNJvcQlf | |
keEhyYvqpncrcxAy+NCa/x1pLBWgOkJ0yEC85CNgLJOvmYj2zBE+y3ZWz9or72bB | |
KyrhnVkY7L3VE7fX0yhrKTsVrbRal/IRm8T8H2RXAxKnacybqEFksEBkS/lezu6S | |
EUVrLVJPPkjUWJypIi+4J9/iDtJ2nkblndlfQTxHgOR1xdpDpPIqRLBX0g+ppm2K | |
jH+LCovln9zKXUaxxLnFZs43XHbiRijsISxHjIVMkY/6c38khX4kFehSJ3LwmTo2 | |
J5g/GvYhP+IaD5dvQGTuvVOP3El1M0nLGLxNo0tYqgwx7gsWdXLxdxWeJio1Z7Up | |
sjWxalaX8sEMYiK+JOlzSM5rDWfrvugviRYQyTFj8XrRyVj6EdqJ5v16ofQRw+0+ |
This is my upload-file
type for what I use at work. We use angular-upload for the upload
service to do the actual file uploading. We also have several abstractions and use ES6 that may confuse you a little bit (sorry about that). Hopefully this gets you started though.
// app/transforms/array.js | |
import Ember from 'ember'; | |
import DS from 'ember-data'; | |
export default DS.Transform.extend({ | |
deserialize: function(value) { | |
if (Ember.isArray(value)) { | |
return Ember.A(value); | |
} else { | |
return Ember.A(); |
/* | |
DS.attr('object') | |
*/ | |
App.ObjectTransform = DS.Transform.extend({ | |
deserialize: function(value) { | |
if (!$.isPlainObject(value)) { | |
return {}; | |
} else { | |
return value; | |
} |
After spending the better part of the month implementing date support | |
in RethinkDB, Mike Lucy sent the team the following e-mail. It would | |
have been funny, if it didn't cause thousands of programmers so much | |
pain. Read it, laugh, and weep! | |
----- | |
So, it turns out that we're only going to support dates between the | |
year 1400 and the year 10000 (inclusive), because that's what boost | |
supports. |