-
Notifications
You must be signed in to change notification settings - Fork 6
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
Create the Asset Database #363
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.
Skimmed through it and left a few comments. In general it looks good to me. Two general suggestions:
-
Can we get shrink down the number of migration files? They've clearly grown as development has happened, but it's quite messy now. You should be able to simply delete them all, then
makemigrations
again to generate a single file. That might break your local databases, but you can just throw them away and generate sample data again -
There are no tests. Ultimately it's up to you, but I would recommend adding at least a few for the basic functionality. They have saved us a few times with RIGS!
One more thing - this branch needs re-basing onto master, or have master merged into it. The latter may be easiest. |
Again. Again again.
Surprisingly, not my fault, it was @mattysmith22
I blame @mattysmith22 again ...
TODO: Make the colour defined by the status as opposed to hardcoding it...
Red is for broken/lost - things we should have but don't Yellow is for sold/scrapped - things we had but don't have on purpose Blue is not built yet because... I don't have a reason for that one.
PR opened for Heroku deployment purposes, it is not quite ready yet!