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

Locations: DB Model update & migration to add location table #463

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

samturner3
Copy link
Contributor

@samturner3 samturner3 commented Aug 27, 2024

It would be great to have 'location' as a separate table, rather than string on a spool.

This will allow us to print labels for locations, then scan a QR code label for a location and see what spools are in said location.

To do:

  • Update DB model to include a new 'location' table

  • Add a migration file to migrate existing locations (in spool) to create new locations and handle non-unique names etc.

  • Add UI screens for location model - including update spool location UI

  • Add a locations page - include view to see list of all spools in a location

  • Re-arrange spools between locations UI (drag and drop?) (stretch goal)

  • Add ability to print labels with QR codes for locations - upon scan show view to see list of all spools in a location

  • Update tests

  • Add test for migration to ensure existing string spool.location create a location object successfully. (Tested and passed manually)

Feedback as I go would be appreciated with and concerns / requests.
See #465 - please provide your thoughts

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.

1 participant