-
-
Notifications
You must be signed in to change notification settings - Fork 696
merge master into vuepress #636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Add "no-unused-components" rule * Handle case with Literal in :is binding expression, update docs * Update no-unused-components.md
...s#546) * Add no-string-prop-type rule - basic implementation * Rename rule * Add more tests, update docs
* Add `vue/no-spaces-around-equal-signs-in-attribute` rule * Add check that error message location is correct. * Fix rule URL
* [New] Add `vue/multiline-html-element-content-newline` rule * Update `ignoreNames` -> `ignores` and report messages
* [New] Add `vue/singleline-html-element-content-newline` rule * Update `strict` -> `ignoreWhenNoAttributes`, `ignoreNames` -> `ignores` and report messages
...noreWhenBindingPresent" option (vuejs#558) * Fix custom component detection * Add ignoreWhenBindingPresent setting to no-unused-components * Make ignoreWhenBindingPresent setting true by default in no-unused-components rule
According to OWASP shorthand XSS stands for Cross-Site Scripting: https://www.owasp.org/index.php/Cross-site_Scripting_(XSS)
* Update "Why doesn't it work on .vue file?" I had an issue where the plugin works, but red markings of errors remained. So I found out the instructions for this section are missing a note regarding Vetur. You need the following setting to complete the setup: ``` "vetur.validation.template": false ``` Note: While it solved my issue, there is something to consider with how it's applied. Eslint is mostly used in a per-project manner. This means, if you apply the rule above to `settings.json`, it is global a rule and Vue projects that do not use this plugin will not show template errors. So to solve this, you need to apply the setting locally. In the context of VS Code, it's easy. You just save a "workspace" to your project root and that creates a file, where you can apply the settings, thus locally. See [here](microsoft/vscode#37519) for details. * Update README.md
... `order-in-components` (vuejs#569) * Fix: if no trailing comma, not to leave trailing comma after fixed of `order-in-components` * use array fixer
* Fixed an issue where the rules `vue/script-indent` unexpected error report whileforce using semicolon. * remove unrelated comment * fixed parse error
* Adding default array example of correct rule * Updating examples for factory functions * Update require-valid-default-prop.md
* Fix vuejs#560 Allow null in require-prop-type-constructor * Add missing check for `{ type: null }`
* Migrate circleci to version 2 * remove legacy eslint-plugin-html * Update config.yml * Update config.yml
* Add typescript specific changes * Add "as" helper * Fix vue/require-default-prop * Fix vue/require-prop-types * Allow to use `export default (Vue as VueConstructor<Vue>).extend({` syntax Fix issues: vuejs#564 vuejs#575 * Fix vue/require-prop-type-constructor * Fix vue/require-valid-default-prop * Add more tests in utils
* Update shields in readme * Update README.md
* Corrected doc name use-v-on-exact * Mistake
@armano2
armano2
changed the title
(削除) Vuepress merge (削除ここまで)
(追記) Merge master into vuepress (追記ここまで)
Nov 9, 2018
@armano2
armano2
changed the title
(削除) Merge master into vuepress (削除ここまで)
(追記) merge master into vuepress (追記ここまで)
Nov 9, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
conflicts resolved