fix(core): properly update execution permalink on location change #7152
Conversation
This file contains 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
anotherchrisberry
added a commit
that referenced
this pull request
Jun 27, 2019
* chore(core): Bump version to 0.0.378 058007e fix(core): properly update execution permalink on location change (#7152) 9bd9624 fix(projects): Fixed project dashboard to application link (#7154) d6ad8c2 feat(appengine): Enable new artifacts for config artifacts in deploy SG (#7153) a9a927b feat(appengine): Enable new artifacts workflow in deploy SG (#7147) * chore(amazon): Bump version to 0.0.195 8ee7e11 fix(amazon): Fix SpEL support for load balancers (#7151)
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.
It looks like the
$stateChangeSuccessevent fires before the browser's location has been updated, so we're always behind a cycle when rendering the permalinks for executions.Moved into a separate component because
<Execution>is already pretty pretty big.EDIT: I added a second commit to cut down on the re-render calls. What we are doing currently is kind of nuts and unnecessary and results in ~8 calls to
renderfor each displayed execution every time a user clicks on a stage to toggle details or switch to a different execution.