-
Notifications
You must be signed in to change notification settings - Fork 34
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
Remove everything to do with topic_needs_review #698
Conversation
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.
LGTM
I have a question though, there's still some refs in the "export_curriculum.py" and "import_curriculum.py" scripts. "topic_needs_review": o.topic_needs_review,, topic_needs_review, should we not remove those too
My thinking was that we already had the objects fetched from the above lines and that accessing them while they're already fetched shouldn't make any new db calls. But I've changed it anyway, just in case. |
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.
This is good, but it's incomplete.
Ther is a topic_needs review field on the ContentItem model. There are a whole lot of things that expect that column to exist. All that stuff must go.
If you are running vscode, open the backend directory and Ctrl+Shift+F to find all mentions of topic_needs_review. Those should all. The only mentions that can remain are those in the api serialisers. Everything else is technical debt
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.
A bunch of tests are failing because of the recent changes.
My bad, I'll have a look. I believe I just ran the frontend tests |
That should do it. Please reply with screenshots if the issue still persists so I know which tests are giving you issues |
Here is one of them, basically ran
|
I don't have any issues running all the tests now. I believe those errors arise because the PR changes the model properties, so migrations must be made. Running: python manage.py makemigrations && python manage.py migrate should resolve the issues. |
Related issues: [please specify]
Description:
What are you up to? Fill us in :)
Screenshots/videos
I solemnly swear that: