-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Lifecycle Diagram inconsistencies #251
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
Comments
Thanks for the suggestion, but here's what I think: The The |
I see what you mean and that difference is depicted by having a green box vs not having one. If you look closely you will notice that will not be changed by what I mean. The way some of the boxes are currently used however breaks all convention. |
* 漢字変換ミス修正 * anchor URLミス修正 * typo修正:原文は正しい * 意味が逆の箇所の訂正 原文:keep-alive is no longer a special attribute, but rather a wrapper component, similar to <transition>
Опечатка в comparison.md
The current lifecycle diagram is a bit inconsistent in a few places:
if
's "no" branch enters the secondif
through one of its exits (its "no"-exit). Instead it should join the main path and enter the secondif
as one common path.if
's "no" exit is already occupied so the actual "yes/no" branch happens below the node. Instead the "no" branch should exit to the right.if
's "no" branch enters "ready" from the side while it should merge with the main path and enter from the top as one common path.if
blocks I think theready
anddestroyed
events should fire before the "Ready" and "Destroyed" states are reached. Right now the fire while the states are reached.I would have posted a PR but there are no sources for the diagram available so I will just post a crude ASCII art of what I mean. Currently it looks like:
when I think it should look like
The text was updated successfully, but these errors were encountered: