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 #603 refactor play to lessons #612

Merged
merged 14 commits into from
Jan 27, 2020

Conversation

PrarabdhGarg
Copy link
Contributor

Fixes #603

Explanation

This pull request completes the refactoring process, refactoring files that were left in the previous pull request.

Checklist

  • [x ] 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: ...".)
  • [x ] The PR explanation includes the words "Fixes #bugnum: ..." (or "Fixes part of #bugnum" if the PR only partially fixes an issue).
  • [x ] The PR follows the style guide.
  • [ x] The PR does not contain any unnecessary auto-generated code from Android Studio.
  • [ x] The PR is made from a branch that's not called "develop".
  • [x ] The PR is made from a branch that is up-to-date with "develop".
  • [ x] The PR's branch is based on "develop" and not on any other branch.
  • [ x] The PR is assigned to an appropriate reviewer in both the Assignees and the Reviewers sections.

As per the new mocks, the paly tab was renamed to lessons.
Hence, the entrire project was refactored, along with tests, to maintain
consistency with mocks.

Resolves oppia#603
@rt4914
Copy link
Contributor

rt4914 commented Jan 21, 2020

@PrarabdhGarg Why was this PR created, as #609 is similar to this one, any specific reason? Also, please close one of these PR's with proper comment of why you are closing it.

@PrarabdhGarg
Copy link
Contributor Author

@rt4914 is it possible to update the previous pull request with the latest changes I have made?

@rt4914
Copy link
Contributor

rt4914 commented Jan 21, 2020

@rt4914 is it possible to update the previous pull request with the latest changes I have made?

Yes it is possible, you just need to make a new commit to that same branch and update it.
For example, your branch name is my-sample-branch. So you do following things,

git checkout my-sample-branch
Now you are in your branch, so make all the changes that you need. After all the changes are finished.

git add .
git commit -m "appropriate commit message"
git push origin my-sample-branch

@PrarabdhGarg
Copy link
Contributor Author

@rt4914 I was not aware of this. Will follow this going forward.
In this case, I had to create a new pull request as you had suggested changing the branch name

@PrarabdhGarg
Copy link
Contributor Author

I will close the previous Pull request

@rt4914
Copy link
Contributor

rt4914 commented Jan 21, 2020

@rt4914 I was not aware of this. Will follow this going forward.
In this case, I had to create a new pull request as you had suggested changing the branch name

Have you taken a look at this document: https://github.com/oppia/oppia-android/wiki#instructions-for-making-a-code-change

This might help.

@PrarabdhGarg
Copy link
Contributor Author

@rt4914 I was not aware of this. Will follow this going forward.
In this case, I had to create a new pull request as you had suggested changing the branch name

Have you taken a look at this document: https://github.com/oppia/oppia-android/wiki#instructions-for-making-a-code-change

This might help.

I will surely read this. Thanks a lot

@PrarabdhGarg PrarabdhGarg mentioned this pull request Jan 21, 2020
2 tasks
@PrarabdhGarg
Copy link
Contributor Author

@rt4914 I have closed the previous pull request

@rt4914
Copy link
Contributor

rt4914 commented Jan 21, 2020

@rt4914 I have closed the previous pull request

@PrarabdhGarg Thanks.

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.

Looks good to me, some final changes are needed.

  1. -> Address all the comments and fix those issues.
  2. -> change play_chapter_view to lessons_chapter_view
  3. -> Second step change will need to update the code in ChapterSummaryAdapter.kt

@@ -157,4 +162,4 @@
</indentOptions>
</codeStyleSettings>
</code_scheme>
</component>
</component>
Copy link
Contributor

Choose a reason for hiding this comment

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

Revert this file. We do not want these changes.

Copy link
Contributor

Choose a reason for hiding this comment

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

@PrarabdhGarg This file is still here. We do not want to make any changes to this file. So please revert back this file to its original code.

@PrarabdhGarg
Copy link
Contributor Author

@rt4914 I have made the required changes

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.

@PrarabdhGarg .idea/codeStyles/Project.xml was not meant to be be deleted. In my earlier comment, by revert I meant that the changes should be reverted and finally the file should be same as before on develop branch.

Also revert .idea/vcs.xml file changes too, we do not need those changes.

.idea/vcs.xml Outdated
</component>
</project>
</project>
Copy link
Contributor

Choose a reason for hiding this comment

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

Please revert this file changes. We do not want these unnecessary changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I will do this. I am sorry for the confusion

Copy link
Contributor

Choose a reason for hiding this comment

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

No issues. To make PRs more effective, before sending the PR for review its nice to go to the pull request, click on "Files Changed" and try to self review it first and whatever mistakes you find, fix them and then send it for review. This will help you a lot in becoming a good developer.

Copy link
Contributor

Choose a reason for hiding this comment

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

Same here. This file changes are also not needed.

@PrarabdhGarg
Copy link
Contributor Author

@rt4914 I have added the files again and made the small changes

@PrarabdhGarg
Copy link
Contributor Author

Are the merge conflicts coming because I didn't update my branch with the latest develop branch? If yes, should I be solving them, or you would be solving them while merging the pull request?

@rt4914
Copy link
Contributor

rt4914 commented Jan 27, 2020

Are the merge conflicts coming because I didn't update my branch with the latest develop branch? If yes, should I be solving them, or you would be solving them while merging the pull request?

It would be nice if we can solve it right now only.

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.

@@ -157,4 +162,4 @@
</indentOptions>
</codeStyleSettings>
</code_scheme>
</component>
</component>
Copy link
Contributor

Choose a reason for hiding this comment

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

@PrarabdhGarg This file is still here. We do not want to make any changes to this file. So please revert back this file to its original code.

.idea/vcs.xml Outdated
</component>
</project>
</project>
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here. This file changes are also not needed.

@PrarabdhGarg
Copy link
Contributor Author

@PrarabdhGarg PTAL

@rt4914 Since I had deleted the files in my previous commit, I just copied the files from the current develop branch, and committed them. I guess now they are the same as that on the develop branch

@PrarabdhGarg
Copy link
Contributor Author

@rt4914 I have also resolved the merge conflicts

@rt4914
Copy link
Contributor

rt4914 commented Jan 27, 2020

@PrarabdhGarg PTAL

@rt4914 Since I had deleted the files in my previous commit, I just copied the files from the current develop branch, and committed them. I guess now they are the same as that on the develop branch

You can go to Files changed tab in this PR and check for following files:
.idea/codeStyles/Project.xml
.idea/vcs.xml

These files are getting changed. We do not want any change to these files.

@rt4914
Copy link
Contributor

rt4914 commented Jan 27, 2020

@rt4914 I have also resolved the merge conflicts

@PrarabdhGarg thanks.

@PrarabdhGarg
Copy link
Contributor Author

@rt4914 I have reverted the files. How do I ensure that any local changes in these files are not pushed in the future? Should I add them to the git ignore file?

@rt4914
Copy link
Contributor

rt4914 commented Jan 27, 2020

@rt4914 I have reverted the files. How do I ensure that any local changes in these files are not pushed in the future? Should I add them to the git ignore file?

Thanks a lot. Actually these files should not be added to git ignore. Also, mostly it should get fixed in your next PR. If it does not get fixed please inform us and we will try to come up with some solution.

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 @PrarabdhGarg

@rt4914 rt4914 merged commit ae5a0c4 into oppia:develop Jan 27, 2020
@PrarabdhGarg PrarabdhGarg deleted the fix-#603-refactor-play-to-lessons branch February 22, 2020 12:35
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.

Play should be updated to Lessons
2 participants