This does *not* mean that svelte is using flow (yet ? :-), it is only
that people using flow for code completion get some meaningful results
instead of flow complaining about a missing .flowconfig file.
The editorconfig is so that people who use spaces by default get their
editor using tabs like expected.
Improves the validator to fail if someone forgets to declare
dependent properties for computed state:
```
export default {
computed: {
bar: () => { return new Date().getTime(); }
}
};
```
* sveltejs/master:
keep target and anchor inside mount method
rename parent to root
Fix typo in generator's contextualise; solves #46
fix onrender hook for nested widgets
add a createAnchor helper
various refactorings & fixes
separate create from mount
* sveltejs/master:
-> v1.0.7
use decodeCharacterReferences in text.js, not tag.js
-> v1.0.6
upgrade magic-string, fix sourcemaps
add .json extension to the ESLint config file
add links to gulp/Metalsmith plugins
more sourcemap stuff
Convert entities of all text nodes
add infrastructure for sourcemap tests
Adding link to Browserify transform
dont use options.filename for original code when generating magicstring bundle (#43)
According to the ESLint release note http://eslint.org/blog/2015/11/eslint-v1.10.0-released#configuration-file-formats):
> We are formally deprecating use of the `.eslintrc` extensionless configuration file format in favor the format-specific versions. Don't worry, we'll still support `.eslintrc` files for a long time, but we'd like to encourage everyone to move to the new file formats as you'll get advantages such as syntax highlighting and error detection with many editors.
Actually, Github doesn't highlight `.eslintrc` contents, but does well for `.eslintrc.yml`.
59681635dc/.eslintrc72e007a88f/.eslintrc.yml