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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't actually redundant, because
setShowSpinner
internally sets the spinner show value tofalse
. It's weird logic I know, but it does its job I think (which is to determine if the state needs to be "switched", since the spinner itself is imperatively created).optimizeComponent
will then run its own spinner lifecycle, showing and hiding the spinner, after which theshowSpinner
value will again bubble up to the transpile operation itself.We only want
opimtimizeComponent
to show the spinner if it actually already was originally being show, determined by theif (showSpinner)
check.It's convoluted sure, but the logic works!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is, if
showSpinner
isfalse
I'm not sure we want to show the spinner? Specifically we need to respectopts.quiet
.