Skip to content

Instantly share code, notes, and snippets.

View typeoneerror's full-sized avatar
🤠
iOS, Capacitor, Ember, Vue, Rails

Benjamin Borowski typeoneerror

🤠
iOS, Capacitor, Ember, Vue, Rails
View GitHub Profile
/* jshint node: true */
var _ = require('lodash');
module.exports = function(deployTarget) {
var ENV = {
build: {}
};
var s3 = {
{
"tenant": {
"id": 2,
"banner_image": null,
"description": "<p>Hi, we're Oki Doki. Oki Doki is a collaboration between digital strategist and teacher <a href=\"http://mariepoulin.com\">Marie Poulin</a> and designer and developer <a href=\"http://typeoneerror.com\">Benjamin Borowski</a>. We craft websites and help our clients grow audiences and online communities; now we've joined forces to create the next evolution of online course creation. We call it, simply, Doki.\n</p>",
"favicon_image": null,
"logo_image": null,
"name": "Oki Doki Digital",
"owner_id": 1,
"privacy_option": "default_privacy",
@typeoneerror
typeoneerror / routes.rb
Created October 8, 2015 17:29
concerns and member routes
concern :uploads do
post 'upload'
delete 'upload/:type', action: :remove_image
end
# POST /topics/:id/uploads
resources :topics do
member do
concerns :uploads
end
{
"type": "object",
"required": ["drip"],
"properties": {
"drip": {
"type": "object",
"additionalProperties": false,
"required": [
"id",
"created_at",

I agree with Monteiro that folks who act reprehensibly should immediately be removed from our spaces. No question. However, I do—as someone who has struggled with mental illness my entire life—have some additional thoughts.

As much as I want—no NEED—to remove harmful individuals from spaces, I find it harmful using "sociopath" to describe bad behavior. I've personally used this word frequently, along with "crazy" and other ableist language. I want to do better.

Speaking with my friend who is a psychologist, she noted "sociopath" and "psychopath" are meaningless words; no agreed-upon definition. Calling someone a "sociopath" is like calling a woman a "slut"; you are labeling based on behavior you don't like or don't understand. Personally, I think it further stigmatizes mental health for people who've been diagnosed with personality disorders. Most of the people I know personally with personality/disaffective disorders are wonderful, caring people, and it's unfair and unclear for them to be lumped in with

@typeoneerror
typeoneerror / recap.md
Last active August 29, 2015 14:27
Recap of Ember.YVR Talks Night on August 10th, 2015

Ember.YVR Talks Night

August 10th, 2015

Just wanted to say thank you again for coming out to our first talks night. Hopefully we can keep the momentum going. If you're like me, you don't have a lot of folks to talk Ember with IRL and the pace of the framework's development can be daunting at times. So let's stick together and learn together.

NEXT UP

The next meetup has already been announced, so join us if you can:

@typeoneerror
typeoneerror / active_model_serializers.rb
Created August 9, 2015 18:48
Getting ember-data to play nice with PATCH and active_model_serializers
# config/initializers/active_model_serializers.rb
ActiveModel::Serializer.config.adapter = ActiveModel::Serializer::Adapter::JsonApi
api_mime_types = %W(
application/vnd.api+json
text/x-json
application/json
)
import Ember from 'ember';
import DS from 'ember-data';
var underscore = Ember.String.underscore;
export default DS.JSONAPISerializer.extend({
keyForAttribute: function(attr) {
return underscore(attr);
},
import Ember from 'ember';
export default Ember.Component.extend({
text: null,
tooltip: null,
didInsertElement: function() {
this.$('[data-toggle=tooltip]').each(function() {
$(this).tooltip({ container: 'body' });
saveSortOrder: function(orderData) {
const url = this.store.apiPathFor('faqs/sort');
const adapter = this.store.adapterFor('faq');
const ajaxOptions = { data: { order: orderData } };
adapter.ajax(url, 'PUT', ajaxOptions).then((response) => {
this.send('toast', 'success', 'Successfully updated FAQ order');
this.store.pushPayload(response);
}, () => {
this.send('toast', 'error', 'Failed to update FAQ order');