Replace apps post-migration signals with data migrations
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 21
- Avg merge
- 5d 19h
- Merged PRs (30d)
- 5
Description
TL;DR: Replace the signals used accounts/apps.py with data migrations at the appropriate point in the sequence.
Narrative
As a new developer beginning to work on Lookit, it would be easier to set up a local database if db entries needed for migrations were created during migrations, rather than in a post-migration signal. This would also be more straightforward and maintainable.
Acceptance criteria
TBD
Implementation Notes
signals are defined in accounts/signals.py.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading accounts/signals.py and the references to it in accounts/apps.py. Trace when those signals run relative to the migration sequence and identify the existing database entries they create. The issue has no defined acceptance criteria, so confirm the intended migration point and completion conditions with maintainers before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100