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 #511 : Past expanded answers do not collapse in the question player #1456

Merged
merged 26 commits into from
Aug 24, 2020

Conversation

anandwana001
Copy link
Contributor

@anandwana001 anandwana001 commented Jul 8, 2020

Explanation

Fixes #511

Added QuestionPlayerActivityLocalTest. Added test cases for the previous header expand and collapse logic both in StateFragment and QuestionPlayer.

Test passing with these test cases

Screenshot 2020-08-20 at 00 25 22

Test fails without this fix

Screenshot 2020-08-20 at 00 23 58

Till here all test are passing in StateFragmentLocalTest

Screenshot 2020-08-20 at 00 28 03

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 PR follows the style guide.
  • The PR does not contain any unnecessary auto-generated code from Android Studio.
  • The PR is made from a branch that's not called "develop".
  • The PR is made from a branch that is up-to-date with "develop".
  • The PR's branch is based on "develop" and not on any other branch.
  • The PR is assigned to an appropriate reviewer in both the Assignees and the Reviewers sections.

Copy link
Member

@BenHenning BenHenning left a comment

Choose a reason for hiding this comment

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

Thanks @anandwana001! I have one overall question that I left a comment on.

Copy link
Member

@BenHenning BenHenning left a comment

Choose a reason for hiding this comment

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

This is awesome, nice find @anandwana001! Since this is really subtle, can we add a GitHub action to test that new code doesn't use certain prohibited patterns like this import?

@anandwana001
Copy link
Contributor Author

This is awesome, nice find @anandwana001! Since this is really subtle, can we add a GitHub action to test that new code doesn't use certain prohibited patterns like this import?

Yes, I can file issue regarding the check you mention with few others custom check we are thinking to good to have.

Copy link
Contributor

@rt4914 rt4914 left a comment

Choose a reason for hiding this comment

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

LGTM, thanks.

@rt4914 rt4914 removed their assignment Jul 29, 2020
@anandwana001
Copy link
Contributor Author

anandwana001 commented Jul 30, 2020

@BenHenning Are we good to merge this PR now?
I had created another issue which will track the addition of custom lint checks we need in our codebase.
#1545

@BenHenning
Copy link
Member

Thanks for filing the issue. I think adding a test should still be a priority since it should be possible.

@BenHenning BenHenning assigned anandwana001 and unassigned BenHenning Aug 1, 2020
@anandwana001 anandwana001 assigned rt4914 and unassigned anandwana001 Aug 20, 2020
@rt4914
Copy link
Contributor

rt4914 commented Aug 21, 2020

@anandwana001 Un-assigning myself until this comment related discussion gets and update #1456 (comment)

@rt4914 rt4914 removed their assignment Aug 21, 2020
Copy link
Member

@BenHenning BenHenning left a comment

Choose a reason for hiding this comment

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

Thanks!

@rt4914 rt4914 merged commit 4ccbf73 into oppia:develop Aug 24, 2020
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.

Past expanded answers do not collapse in the question player
3 participants