Migrate exploration and question to use the new translation structure

DubeySandeep commented 1 year ago

Overview

This PR does the following: Migrates exploration and question to use the new translation structure
Essential 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 linter/Karma presubmit checks have passed locally on your machine.
[x] "Allow edits from maintainers" is checked. (See here for instructions on how to enable it.)
- This lets reviewers restart your CircleCI tests for you.
[ ] The PR is made from a branch that's not called "develop".

Proof that changes are correct

Proof of changes on desktop with slow/throttled network

Exploration Editor

https://user-images.githubusercontent.com/16653571/189296853-d88e3fe5-a071-4c2a-af3e-85a979ee0098.mp4

Exploration player

https://user-images.githubusercontent.com/16653571/189297307-4be210fe-7392-4ac7-ab34-a247663ce6fa.mp4

Question editor and player

https://user-images.githubusercontent.com/16653571/189298200-095f7202-e1ba-4155-a57a-970a2fb11e6c.mp4

PR Pointers

Make sure to follow the instructions for making a code change.
If you need a review or an answer to a question, and don't have permissions to assign people, leave a comment like the following: "{{Question/comment}} @{{reviewer_username}} PTAL". Oppiabot will help assign that person for you.
For what code owners will expect, see the Code Owner's wiki page.
Make sure your PR follows conventions in the style guide, otherwise this will lead to review delays.
Never force push. If you do, your PR will be closed.
Some of the e2e tests are flaky, and can fail for reasons unrelated to your PR. We are working on fixing this, but in the meantime, if you need to restart the tests, please check the "If your build fails" wiki page.

oppiabot[bot] commented 1 year ago

Hi, @DubeySandeep, this pull request does not have a "CHANGELOG: ..." label as mentioned in the PR pointers. Assigning @DubeySandeep to add the required label. PRs without this label will not be merged. If you are unsure of which label to add, please ask the reviewers for guidance. Thanks!

oppiabot[bot] commented 1 year ago

Hi @vojtechjelinek, PTAL at this PR, it adds a new job. The name of the job is RegenerateContentIdForTranslationSuggestionsInReviewJob.
Also @DubeySandeep, please make sure to fill in the server jobs form for the new job to be tested on the backup server. This PR can be merged only after the test run is successful. Please refer to this guide for details.
Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue. If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

kevintab95 commented 1 year ago

@DubeySandeep could you provide some steps on how to reproduce the error / issue (https://github.com/oppia/oppia/pull/15837#issuecomment-1217059664) you are facing with this PR?

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue. If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!

oppiabot[bot] commented 1 year ago

Hi, @DubeySandeep, this pull request does not have a "CHANGELOG: ..." label as mentioned in the PR pointers. Assigning @DubeySandeep to add the required label. PRs without this label will not be merged. If you are unsure of which label to add, please ask the reviewers for guidance. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

DubeySandeep commented 1 year ago

@kevintab95 Can you take a review pass on the backend files?

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Unassigning @srijanreddy98 since the review is done.

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

DubeySandeep commented 1 year ago

@kevintab95 I've replied to your comments, PTAL!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, there is a new change in develop which needs to be in your PR. Please update your branch with the latest changes in develop. For instructions, refer to this link. Thanks!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep, the build of this PR is stale and this could result in tests failing in develop. Please update this pull request with the latest changes from develop. Thanks!

DubeySandeep commented 1 year ago

If there are more changes (e.g. issues fixed as part of testing), please let me know and I can review them ASAP. What is the next step in this PR?

Sure, I'll let you know after completing the testing on backup server!

oppiabot[bot] commented 1 year ago

Hi @DubeySandeep. 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!

oppia / oppia