| function kinopioExtension() { | |
| let dataAttr = 'data-kinopio-extension-by-dnrvs' | |
| function processCard(container, node, text) { | |
| // Clean out old nodes | |
| container.querySelectorAll(`[${dataAttr}]`).forEach(n => n.remove()) | |
| // Clone the real one |
This gist will no longer be updated as the changelog will be on the official website.
Converted via https://domchristie.github.io/turndown
A guide to our Swift style and conventions.
This is an attempt to encourage patterns that accomplish the following goals (in rough priority order):
Reference: Sequelize docs on association
Let’s say we have two models: Films and Festivals
We know that a film can be shown at many film festivals and that, conversely, a festival can show many films. This is what is known as a many-to-many relationship.
Knowing this, we can set up our associations:
| <html> | |
| <body> | |
| <h4>websocket</h4> | |
| <h5>Group: <span id="group">darwin</span></h5> | |
| <!-- a hardoced group name --> | |
| <button onclick="bjoin();">join group</button><br> | |
| <input id="text" type="text"/> | |
| <span id="out"></span> | |
| <script> | |
| var group=document.getElementById("group").textContent; |
When querying your database in Sequelize, you'll often want data associated with a particular model which isn't in the model's table directly. This data is usually typically associated through join tables (e.g. a 'hasMany' or 'belongsToMany' association), or a foreign key (e.g. a 'hasOne' or 'belongsTo' association).
When you query, you'll receive just the rows you've looked for. With eager loading, you'll also get any associated data. For some reason, I can never remember the proper way to do eager loading when writing my Sequelize queries. I've seen others struggle with the same thing.
Eager loading is confusing because the 'include' that is uses has unfamiliar fields is set in an array rather than just an object.
So let's go through the one query that's worth memorizing to handle your eager loading.
| target = $('body') | |
| # get random RGB values so we can change background and link colors | |
| r = Math.floor Math.random() * 241 | |
| g = Math.floor Math.random() * 241 | |
| b = Math.floor Math.random() * 241 | |
| # variables to hold the lighter shade RGB values | |
| # rp1; gp1; bp1; rp2; gp2; bp2; rp3; gp3; bp3 |
| # bouncy links | |
| $('a').each -> | |
| $(this).mousemove (e) -> | |
| if this.isAlreadyAnimating | |
| console.log 'still animating: ', this.isAlreadyAnimating | |
| else | |
| baseExpX = 4 # 2 ^ 4 == 16 | |
| baseExpY = 2 # 2 ^ 4 == 16 |
| const randomColor = (() => { | |
| "use strict"; | |
| const randomInt = (min, max) => { | |
| return Math.floor(Math.random() * (max - min + 1)) + min; | |
| }; | |
| return () => { | |
| var h = randomInt(0, 360); | |
| var s = randomInt(42, 98); |
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
