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

Create the Asset Database #363

Merged
merged 122 commits into from
Dec 4, 2019
Merged

Create the Asset Database #363

merged 122 commits into from
Dec 4, 2019

Conversation

FreneticScribbler
Copy link
Member

PR opened for Heroku deployment purposes, it is not quite ready yet!

@davidtaylorhq davidtaylorhq temporarily deployed to pyrigs-pr-363 November 24, 2019 14:37 Inactive
@mattysmith22 mattysmith22 temporarily deployed to pyrigs-pr-363 November 25, 2019 13:41 Inactive
Copy link
Contributor

@davidtaylorhq davidtaylorhq left a 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:

  1. 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

  2. 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!

RIGS/migrations/0035_auto_20191008_2148.py Outdated Show resolved Hide resolved
assets/api.py Outdated Show resolved Hide resolved
assets/management/commands/deleteSampleData.py Outdated Show resolved Hide resolved
requirements.txt Outdated Show resolved Hide resolved
requirements.txt Outdated Show resolved Hide resolved
@davidtaylorhq
Copy link
Contributor

One more thing - this branch needs re-basing onto master, or have master merged into it. The latter may be easiest.

@mattysmith22 mattysmith22 temporarily deployed to pyrigs-pr-363 December 4, 2019 20:13 Inactive
Again. Again again.
@davidtaylorhq davidtaylorhq temporarily deployed to pyrigs-pr-363 December 4, 2019 20:25 Inactive
@davidtaylorhq davidtaylorhq temporarily deployed to pyrigs-pr-363 December 4, 2019 20:29 Inactive
@davidtaylorhq davidtaylorhq temporarily deployed to pyrigs-pr-363 December 4, 2019 20:39 Inactive
@davidtaylorhq davidtaylorhq temporarily deployed to pyrigs-pr-363 December 4, 2019 20:47 Inactive
@FreneticScribbler FreneticScribbler marked this pull request as ready for review December 4, 2019 20:57
TODO: Make the colour defined by the status as opposed to hardcoding it...
@davidtaylorhq davidtaylorhq temporarily deployed to pyrigs-pr-363 December 4, 2019 21:12 Inactive
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.
@davidtaylorhq davidtaylorhq temporarily deployed to pyrigs-pr-363 December 4, 2019 21:28 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

None yet

5 participants