var state = {
id: 1,
points: 100,
name: "Goran"
};
var newState = {
I hava a folder inside CustomerDocuments in Firebase cloud storage name xyz which contains many types of file like .pdf,.txt,.png etc. | |
function deletefromstorage(quoteiddelete) | |
{ | |
//quoteiddelete contains folder name in CustomerDocuments which we want to delete. | |
const Storage = require('@google-cloud/storage'); | |
const storage = new Storage(); | |
const srcBucketName = 'abc.apot.com'; |
[alias] | |
s = status | |
co = checkout | |
cob = checkout -b | |
del = branch -D | |
br = branch --format='%(HEAD) %(color:yellow)%(refname:short)%(color:reset) - %(contents:subject) %(color:green)(%(committerdate:relative)) [%(authorname)]' --sort=-committerdate | |
save = !git add -A && git commit -m 'chore: savepoint' | |
undo = reset --soft HEAD~ | |
delete = push origin --delete | |
pull-updates = "!f() { (git stash && git checkout $1 && git pull --rebase && git checkout $2 && git rebase $1 && git stash pop) }; f" |
// Import all | |
import Rx from "rxjs/Rx"; | |
Rx.Observable | |
.interval(200) | |
.take(9) | |
.map(x => x + "!!!") | |
.bufferCount(2) | |
.subscribe(::console.log); |
Go to the egghead website, i.e. Building a React.js App
run
$.each($('h4 a'), function(index, video){
console.log(video.href);
});
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?
This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].
We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.
Each commit message consists of a header, a body, and a footer.
These rules are adopted from the AngularJS commit conventions.
These are all the JSConf 2014 slides, codes, and notes I was able to cull together from twitter. Thanks to the speakers who posted them and thanks to @chantastic for posting his wonderful notes.
Thanks a ton for coming down to my talk, folks <33z. Your energy was amazing. This page has a few extra resources for you.