Don't detach pre-existing HTML when view's el is already in the region #3260
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.
Resolves #3227
This PR also moves some of
Region.show
into a_setupChildView
function which mirrors what is happening in a CollectionView currently and helps reduce the length of theshow
function which grew to handle the should empty check. Additionally moved thecurrentView = view
toshow
to make the attach functions between CollectionView and Region more similar.In the specs, there was a failing test regarding “when setting the "replaceElement" class option”. I believe this test was failing because it was reusing
this.view
which wasn’t cleaned up in a prior test. So effectivelythis.view
was currently already shown in another region. I switched this tothis.view1
which is instantiated as part of thisdescribe
block (or closer at least) and should be better for these tests.