Repository navigation
Removing restangular - #3595
Removing restangular#3595
Conversation
4631e74 to
855943f
Compare
|
Refer to this link for build results (access rights to CI server needed): |
mitchell852
left a comment
There was a problem hiding this comment.
still reviewing but here's what i've found so far
|
Refer to this link for build results (access rights to CI server needed): |
mitchell852
left a comment
There was a problem hiding this comment.
lots of stuff broken. better retest.
36e9ad8 to
34bad7c
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
There was a problem hiding this comment.
this whole timeout thing is weird. maybe it can be removed. i'll test it out. can't remember why i put it in here.
There was a problem hiding this comment.
When I remove it it also doesn't show up messages
|
the more I think about it, I think this PR is just way too big / risky. it requires a lot of positive and negative testing to ensure it does not change/break functionality. imo you should tackle one "service" at a time. i.e. remove the use of restangular from cdnservice.js. and move down the list of "services" with a seperate PR until nothing uses restangular and the dependency can be removed altogether. otherwise, the risk is much too high given that TP doesn't have comprehensive regression tests in place. |
|
Alright man, you asked for it I'm gonna leave this open as a draft - I'll rebase once the others are all merged and this will be the one that actually removes restangular entirely. |
72420af to
e1ea540
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
@ocket8888 to rebase |
e1ea540 to
f9b1599
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
mitchell852
left a comment
There was a problem hiding this comment.
make sure to remove from traffic_portal/grunt/browserify2.js as well
985fce7 to
8109386
Compare
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
|
Refer to this link for build results (access rights to CI server needed): |
What does this PR (Pull Request) do?
Removes a dependency that Traffic Portal had on Restangular.
Which Traffic Control components are affected by this PR?
Traffic Portal dependencies are not individually documented, and so no 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