If two view use the same controller name, switching between the two view will result in the initialization and delete operation simultaneously. - #225
Open
zhy1 wants to merge 1 commit into
Conversation
… two view will result in the initialization and delete operation simultaneously.
Collaborator
|
@zhy1 I am trying to understand the problem you are solving here, are you saying that you are naming a two wizards the same name? If so it seems like it would be a better practice to just not do so. Is there an Issue open relating to this PR? Are any others in the community having this issue? Also can you please rebase your branch from the current master, it will solve the CI build issues. |
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
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.
If two view use the same controller name, switching between the two view will result in the initialization and delete operation simultaneously.
version 1
in controller
$scope.pageName=$state.current.name;in view
<wizard name="{{pageName}}"version 2
in controller
do nothing.
in view
do nothing.