Update latest docs 15-02-2019 #1
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
* #1087 Implement search page * Fix spacing and add https in search page * Add sponsors and push history state when search is updated in search page * Add EOL to search styles * Visit first result when submitting search form * Add 'search by algolia' to search page
`is` prop for dynamic components expects a globally registered name of component or component’s options object demonstrated in this [fiddle](https://jsfiddle.net/chrisvfritz/b2qj69o1/).
The inject docs said that the value of an inject object can be an object with a `name` and `default` property, but it should be `from` and `default`.
Removed an extra 's' to fix a grammatical mistake
* Add presentation role to style-only li item
* Update todo-list-example for a11y * Implement review suggestions * Use explicit label instead of aria-label * Move v-model directive to top for improved readability
* change NODE_ENV to follow recommendations from weback * Update deployment.md
* Update components.md * Update components.md * improve flow of single root component section
* cookbook entry for storage * minor tweak * updates to article * updates to article * maybe the last tweak * the honest to god really last mod
… (#1646) @BlitZz96 brought up a good point in [this issue](#1644) about users lacking the necessary background knowledge to fully understand Passing Static and Dynamic Props, at least as it relates to booleans and potentially other types in the future. To fix this, I added a new Prop Types section right before it.
* First stab at SFC to npm documentation * Clean up sample code, clarify .vue usage with SSR builds * Run build tasks in parallel, fix dependency order * Backtick all instances of .vue, minor edits for clarity * Fix typo on link * Update url to vue-sfc-rollup utility in acknowledgements * Fix order, other edits suggested by @sdras * Additional explanation about sfc-to-npm recipe package.json
The phrase "These state management patterns and even Redux itself can be easily integrated into Vue applications" has a link to a deprecated project. Instead I link to a yarnpkg.com search I saw used in https://vuejs.org/v2/guide/state-management.html, which links all "redux vue" projects (so it's always up to date)
* vuejs-templates/* is deprecated because of Vue CLI 3 * vue-touch has been depreceated because of lack of development
Added myself as a community partner 
* Use highlight.js for more semantics * Update hexo version * More tweaks * Better formatting * Fix wrong section seperation
… (#1969) * Add note to the guide * Update example, removing `class` attribute to avoid confusion
This reverts commit f639b83.
[In Review] 2.6 Updates
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.
No description provided.