- node
- npm
module.exports = { | |
"env": { | |
"browser": true | |
}, | |
"extends": "angular", | |
"rules": { | |
"indent": [ | |
1, | |
2 | |
], |
<!DOCTYPE html> | |
<html> | |
<head> | |
<title>Calendar</title> | |
<style> | |
div.input { | |
margin-bottom: 10px; | |
} | |
.month { |
Vue is positioned as progressive javascript frontend framework. It is inspired of MVVM pattern, so no controllers here. I'd like to say vue app is kind of event-driven.
We have 2 ways of structuring the code:
npm install ripple-lib
node tx.js DESTINATION_ADDR SOURCE_ADDR SOURCE_SECRET AMOUNT
0x3147f27ab9f15368982e64f872a2259a4df479a8 |
0x06c0cac3b5a0cefb2445b077a0458cbb38cbd687 |
Column order had a big performance impact on some of the databases I've tuned, spanning Sql Server, Oracle, and MySQL. This post has good rules of thumb:
I hereby claim:
To claim this, I am signing this object:
If you hate git submodule
, then you may want to give git subtree
a try.
When you want to use a subtree, you add the subtree to an existing repository where the subtree is a reference to another repository url and branch/tag. This add
command adds all the code and files into the main repository locally; it's not just a reference to a remote repo.
When you stage and commit files for the main repo, it will add all of the remote files in the same operation. The subtree checkout will pull all the files in one pass, so there is no need to try and connect to another repo to get the portion of subtree files, because they were already included in the main repo.
Let's say you already have a git repository with at least one commit. You can add another repository into this respository like this: