Skip to content
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 #3677: Changes refreshSettingTab function to fix the loading issue with the e2e test. #7526

Merged
merged 5 commits into from
Sep 8, 2019

Conversation

Showtim3
Copy link
Contributor

Explanation

Fix #3677: So the the settingsTab.template.html changes are inspired from PR 6755, and I have wrote a e2e test for the same.

Checklist

  • The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
  • The PR explanation includes the words "Fixes #bugnum: ..." (or "Fixes part of #bugnum" if the PR only partially fixes an issue).
  • The linter/Karma presubmit checks have passed.
    • These should run automatically, but if not, you can manually trigger them locally using python -m scripts.pre_commit_linter and bash scripts/run_frontend_tests.sh.
  • The PR is made from a branch that's not called "develop".
  • The PR has an appropriate "PROJECT: ..." label (Please add this label for the first-pass review of the PR).
  • The PR has an appropriate "CHANGELOG: ..." label (If you are unsure of which label to add, ask the reviewers for guidance).
  • The PR follows the style guide.
  • The PR addresses the points mentioned in the codeowner checks for the files/folders changed. (See the codeowner's wiki page.)
  • The PR is assigned to an appropriate reviewer.
    • If you're a new contributor, please ask on Gitter for someone to assign a reviewer and don't tick this checkbox.
    • If you're not sure who the appropriate reviewer is, please assign to the issue's "owner" -- see the "talk-to" label on the issue. Do not only request the review but also add the reviewer as an assignee.

@Showtim3 Showtim3 closed this Aug 31, 2019
@Showtim3 Showtim3 deleted the reflectEdtiorChanges branch August 31, 2019 21:32
@Showtim3 Showtim3 restored the reflectEdtiorChanges branch August 31, 2019 21:34
@Showtim3 Showtim3 reopened this Aug 31, 2019
@oppiabot
Copy link

oppiabot bot commented Sep 1, 2019

Assigning @nithusha21 for the first-pass review of this pull request. Thanks!

@kevinlee12
Copy link
Contributor

@Showtim3 please don't force push :)

@codecov
Copy link

codecov bot commented Sep 1, 2019

Codecov Report

Merging #7526 into develop will increase coverage by 10.16%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop    #7526       +/-   ##
============================================
+ Coverage    73.27%   83.43%   +10.16%     
============================================
  Files          893     1099      +206     
  Lines        39176    63195    +24019     
  Branches      3617     3617               
============================================
+ Hits         28704    52723    +24019     
  Misses        9316     9316               
  Partials      1156     1156
Flag Coverage Δ
#backend 100% <ø> (?)
#frontend 73.27% <ø> (ø) ⬆️
Impacted Files Coverage Δ
core/domain/user_jobs_continuous.py 100% <0%> (ø)
extensions/issues/base.py 100% <0%> (ø)
core/domain/state_domain.py 100% <0%> (ø)
extensions/rich_text_components/components.py 100% <0%> (ø)
core/domain/skill_domain.py 100% <0%> (ø)
core/domain/visualization_registry.py 100% <0%> (ø)
core/storage/suggestion/gae_models.py 100% <0%> (ø)
extensions/visualizations/models.py 100% <0%> (ø)
core/controllers/cron.py 100% <0%> (ø)
core/platform/image/gae_image_services.py 100% <0%> (ø)
... and 196 more

@codecov
Copy link

codecov bot commented Sep 1, 2019

Codecov Report

Merging #7526 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #7526   +/-   ##
========================================
  Coverage    83.63%   83.63%           
========================================
  Files         1104     1104           
  Lines        64007    64007           
  Branches      3621     3621           
========================================
  Hits         53530    53530           
  Misses        9318     9318           
  Partials      1159     1159
Flag Coverage Δ
#backend 100% <ø> (ø) ⬆️
#frontend 73.3% <ø> (ø) ⬆️

@Showtim3
Copy link
Contributor Author

Showtim3 commented Sep 1, 2019

@kevinlee12 hey m sorry for that, It's a habit i picked up at work to have maximum one commit per PR. Anyways, I'll keep that in mind.

@kevinlee12
Copy link
Contributor

Okay, just make sure to be careful in the future.

@oppiabot
Copy link

oppiabot bot commented Sep 4, 2019

Hi @Showtim3. Due to recent changes in the "develop" branch, this PR now has a merge conflict. Please follow this link if you need help resolving the conflict, so that the PR can be merged. Thanks!

Copy link
Contributor

@nithusha21 nithusha21 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM from my perspective. not very sure about the changes to settingsTab.js however!

expInput.sendKeys(element, protractor.Key.ENTER);
});

const saveChangesButton = element(by.css(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This block is not very readable. Can you add newlines in between logical block of statements?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

@@ -139,6 +139,18 @@ var createAndPublishExploration = function(
publishExploration();
};

var createAddAndPublish = function(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pick a more descriptive name. Create, add (what?) and publish what? I think it should be something like createAddIneractionAndPublishExp()

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@nithusha21
Copy link
Contributor

@DubeySandeep can you PTAL as a codeowner. I am not sure about the changes to your files!

Copy link
Contributor

@kevinlee12 kevinlee12 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have one nit, @nithusha21 covered most of it.

};

ctrl.refreshSettingsTab = function() {
// Ensure that ExplorationStatesService has been initialized before
// getting the state names from it. Otherwise, navigating to the
// getting the state names from it. (Otherwise, navigating to the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove (

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@kevinlee12 kevinlee12 removed their assignment Sep 5, 2019
Copy link
Contributor

@DubeySandeep DubeySandeep left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM for the code owner file.

@DubeySandeep DubeySandeep assigned Showtim3 and unassigned DubeySandeep Sep 7, 2019
@kevinlee12 kevinlee12 merged commit 2125d5f into oppia:develop Sep 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Tags and category field values not appearing under certain circumstances
4 participants