Convert build update page from AngularJS to Vue#1561
Merged
williamjallen merged 1 commit intoJul 14, 2023
Conversation
williamjallen
force-pushed
the
build-update-vue-conversion
branch
from
fa26a80 to
beedb84
Compare
williamjallen
force-pushed
the
build-update-vue-conversion
branch
3 times, most recently
from
55e3fd5 to
bc06c80
Compare
williamjallen
force-pushed
the
build-update-vue-conversion
branch
from
bc06c80 to
1d9203e
Compare
josephsnyder
approved these changes
Jul 14, 2023
Member
josephsnyder
left a comment
josephsnyder
left a comment
There was a problem hiding this comment.
New route looks good, can't see any changes on the page.
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
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
2 participants
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.
This PR is part of our ongoing effort to migrate from AngularJS to Vue. There should be no functionality differences between the old and new versions of the page, beyond a new
/build/<id>/updateroute.