chore(populate_db): migrate assigned dev seed data from JSON to YAML (#2010)#2011
Conversation
✅ Deploy Preview for activist-org ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Thank you for the pull request! ❤️The activist team will do our best to address your contribution as soon as we can. The following are some important points:
Note activist uses Conventional Comments in reviews to make sure that communication is as clear as possible. |
Maintainer ChecklistThe following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)
|
andrewtavis
left a comment
There was a problem hiding this comment.
Approving assuming tests pass ✅
praise: Thanks for the quick work here, @Ayananth! Really a nice addition that will make it easier for us to do presentations with specific data in the future :)
One thing that I'm thinking is that it would be nice to have the activist organization be filtered as the top organization in dev mode so that we're always dogfeeding the platform in dev mode. Maybe you'd want to look into this? I'll make an issue and ping you! 😊
Contributor checklist
Description
This PR switches the dev environment seed data used by the
populate_dbcommand from JSON to YAML to make the data easier to read and maintain.Changes include:
populate_dbcommand to load assigned seed data usingyaml.safe_loadinstead of thejsonmodule.backend/core/management/commands/entity_data_to_assign.jsonto YAML.backend/tests/fixtures/populate_db_assigned.jsonto YAML.--yaml-data-to-assignas the primary CLI argument.--json-data-to-assignas a deprecated alias for backward compatibility.docker-compose.ymlto pass the YAML seed file.pyyamlas a dependency and updateduv.lock.This makes the seed data easier to edit and maintain while preserving backward compatibility.
Related issue
Closes #2010