| # In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env | |
| # variable pointing GPG to the gpg-agent socket. This little script, which must be sourced | |
| # in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start | |
| # gpg-agent or set up the GPG_AGENT_INFO variable if it's already running. | |
| # Add the following to your shell init to set up gpg-agent automatically for every shell | |
| if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then | |
| source ~/.gnupg/.gpg-agent-info | |
| export GPG_AGENT_INFO | |
| else |
| @echo off | |
| powershell -NoProfile -ExecutionPolicy ByPass -File "%~d0%~p0%~n0.ps1" |
| alias nom='npm cache clean && rm -rf node_modules && mkdir node_modules && touch node_modules/.metadata_never_index && npm install' | |
| alias bom='bower cache clean && rm -rf bower_components && mkdir bower_components && touch bower_components/.metadata_never_index && bower install' |
| import Ember from 'ember'; | |
| import { helper } from 'ember-helper'; | |
| import { htmlSafe } from 'ember-string'; | |
| const { escapeExpression } = Ember.Handlebars.Utils; | |
| /** | |
| * This helper escapes a value, useful for building styles | |
| * | |
| * @example | |
| * <div style={{escape (concat 'color:' ugcColour)}}></div> |
In Ember, always use {{...}}, not {{{...}}}. Use Ember.String.htmlSafe as necessary in JavaScript (usually in a component)
to mark markup as HTML-safe. Never pass user-entered content directly to Ember.String.htmlSafe.
Ember has great XSS protection built in. The HTMLBars templating library will automatically run any interpolations through
htmlEscape for you. So
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
If you have a package where a lot of people are still using a legacy version of it you might want to keep pushing (security-)fixes to that "branch".
Let's say the "latest" version of your package is "5.4.0", but there is as significant amount of people still using "4.7.4" – the last version you released before doing "5.0.0".
You found a critical bug in "5.4.0" and push it as out as "5.4.1", but it applies to "4.7.4" as well and so you want to do "4.7.5".
Assuming you have semantic-release already set up, you can follow these steps to get that "4.7.5" legacy support release out.
git checkout v4.7.4git checkout -b 4.x (You can choose any branch name, just make sure to use the same in step 3)
| /* To add more icons just copy these three lines */ | |
| .icon-tomato, | |
| .icon-left-tomato:before, | |
| .icon-right-tomato:after{ | |
| background-image: url(https://s3-us-west-2.amazonaws.com/s.cdpn.io/131442/tomato.svg); | |
| } | |
| #!/usr/bin/env bash | |
| # A basic Self Signed SSL Certificate utility | |
| # by Andrea Giammarchi @WebReflection | |
| # https://www.webreflection.co.uk/blog/2015/08/08/bringing-ssl-to-your-private-network | |
| # # to make it executable and use it | |
| # $ chmod +x certificate | |
| # $ ./certificate # to read the how-to |
Use these rapid keyboard shortcuts to control the GitHub Atom text editor on macOS.