-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: force LMS url to reload when changed #136
fix: force LMS url to reload when changed #136
Conversation
Thanks for the pull request, @ghassanmas! Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
68cd4d9
to
9791014
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #136 +/- ##
==========================================
+ Coverage 95.75% 95.96% +0.21%
==========================================
Files 165 170 +5
Lines 1436 1486 +50
Branches 255 274 +19
==========================================
+ Hits 1375 1426 +51
+ Misses 56 55 -1
Partials 5 5
☔ View full report in Codecov by Sentry. |
label: core contributor |
@ghassanmas Thanks for your contribution! Except for needing a rebase, it looks like this is ready for review? |
9791014
to
9f3af88
Compare
@itsjeyd yes you are correct, I have rebased it, also fixed a similar issue found while testing it. It's now ready for review. |
b41fbca
to
010b2c8
Compare
@mattcarter This PR is ready for review by Aurora. |
010b2c8
to
98f28d5
Compare
For refrence this should be added to: |
91eb62d
to
ded6b25
Compare
This branch has been rebased more than 5 times, should I keep an eye on it? is rebasing necessary assuming it doens't cause conflict? |
@ghassanmas Good question. The PR branch should be up-to-date with CC @mphilbrick211, in case you have any additional input to share here. |
ded6b25
to
fe0eed8
Compare
@itsjeyd Understandable, frankly the situation seems like, you need to wait for the bus in a cold weather, so you plan to leave your house at the time you would wait the least for the bus. Albeit here a timeable for the bus schedule doesn't exist 😄. |
fe0eed8
to
75c6d58
Compare
@ghassanmas You're not wrong 😅 The situation should change once this repo joins the maintainership program. |
@itsjeyd @ghassanmas If the branch becomes out-of-date because we're waiting on a reviewer, the repo owner/merger should be able to fix the date issue before merging - that way, you don't need to keep rebasing as changes to the master happen. Hope this helps! |
|
@ghassanmas I'm not sure about the fork question (maybe Tim can weigh in here - I'm not sure if it would make a difference if it's a fork or not), but re: Waiting for Author... The LABEL "Waiting for Author" is used when we're waiting on the author to answer a question, usually when the PR is already in review, or in the early stages of the PR if more information is needed. The STATUS "Waiting for Author" means the PR is still in-progress and not yet ready-for-review. |
8d91a12
to
a51953b
Compare
@mphilbrick211 If I understand you correctly then, this label shall not be used when "branch becomes out-of-date"? |
Sounds good @arbrandes, thanks for the info. @mattcarter An early heads-up that this will require a second look from Aurora once Adolfo is done with his review. |
@ghassanmas, do you mind updating this to resolve conflicts? I'm planning to review it ASAP. |
@arbrandes I have resolved locally and pushed, but github isn't getting it, checkig the status of github, it seems it's down |
749239a
to
f17a376
Compare
It's ready now, the diff coverage is failing after rebase hence this #152 (comment) |
f17a376
to
a88cb0e
Compare
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.
One minor requested change, otherwise LGTM. I tested it with Tutor and it works.
Oh, and @ghassanmas, is there anything you can do to not reduce the project coverage? |
Just change makes it possible if LMS_BASE_URL is updated by dynamic config to get the latest value.
when platformSettings.courseSearchUrl is relative which is returned from a call to api/learner_home/init, use LMS_BASE_URL as origin. This fixes uses the same pattern which already used for different url, this probably wasn't an issue for edx.org given platformSettings.courseSearchUrl value is abosulte at edx.org
a88cb0e
to
ce88d29
Compare
@arbrandes the diff was because of previous rebaese, now the lastest rebase it might be resolved, otherwise we see what we can do. |
@arbrandes it's now ready the code cov is back as it was hence #136 (comment) it was just edited and previous negative diff comment got delete. |
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.
Can't find anything else to object to, thanks @ghassanmas!
@muselesscreator, what do you think?
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.
seems reasonable to me :-)
@ghassanmas 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
@ghassanmas, mind backporting to Palm? |
What does this change do:
1- This change makes it possible if LMS_BASE_URL is updated by dynamic config to get the latest value. see context below resolved in first commit
2- It make contacte course search url when it's relative resolved in second commit
Testing:
While using tutor-mfe
master
branch it will not work, while when using thisbranch
shall fix it from step 1 you can alter repository and versoin valuesMore context
Fixes that are simlar to this