This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Removed restangular from CoordinateService#3609
Merged
mitchell852 merged 2 commits intoJul 26, 2019
Merged
Conversation
c246720 to
5159363
Compare
Contributor
|
Refer to this link for build results (access rights to CI server needed): |
mitchell852
approved these changes
Jun 25, 2019
Member
mitchell852
left a comment
There was a problem hiding this comment.
UI tests pass
Manual coordinate tests pass
5159363 to
032606f
Compare
Contributor
|
Refer to this link for build results (access rights to CI server needed): |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What does this PR (Pull Request) do?
Removes a dependency on Restangular from the "CoordinateService"
Which Traffic Control components are affected by this PR?
Traffic Portal dependencies are not individually documented, and so no documentation changes are necessary.
What is the best way to verify this PR?
No functionality should have changed (except that errors will now be logged instead of ignored in many cases), so the existing tests should all pass.
Jeremy: actually, the only way to truly verify that the functionality did not change is to:
The following criteria are ALL met by this PR