Skip to content

Add a note about v-else caveat with components and v-show #299

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 2 commits into from
May 11, 2016

Conversation

posva
Copy link
Member

@posva posva commented May 10, 2016

Refers to vuejs/vue#2639

@posva posva force-pushed the v-show-else-caveat branch from 0dbcf98 to 53b5b94 Compare May 10, 2016 22:01
@posva
Copy link
Member Author

posva commented May 10, 2016

Should I add a not to the API too?

@yyx990803
Copy link
Member

Just a link in the API should be enough

@posva posva force-pushed the v-show-else-caveat branch from acae29b to 097fddb Compare May 11, 2016 09:37
@posva
Copy link
Member Author

posva commented May 11, 2016

I noticed there's already a See also link in the api that refers to the v-else guide. Nevertheless I added a second one because it looks more explicit to me and draws user attention because of the word caveat

@yyx990803 yyx990803 merged commit 7998ccc into vuejs:master May 11, 2016
kazupon pushed a commit to kazupon/vuejs.org that referenced this pull request Oct 2, 2016
* Add a note about v-else caveat with components and v-show

Refers to vuejs/vue#2639

* Make component + v-else caveat linkable. Add link in API
kazupon pushed a commit to kazupon/vuejs.org that referenced this pull request Oct 1, 2017
* change on the 'fly' to 'client' to avoid idioms
pick up from 1c0ab87

* update timestamp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants