-
-
Notifications
You must be signed in to change notification settings - Fork 781
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
Refactor states/status #4857
Refactor states/status #4857
Conversation
@SchrodingersGat this would be ready for a review. I moved the database additions to a new PR as this one is becoming big and hard to review with the database components intertwined. |
@matmair looking now, sorry I didn't respond to your previous ping. |
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.
LGTM in general, but there's a lot of files touched :)
InvenTree/order/migrations/0096_alter_returnorderlineitem_outcome.py
Outdated
Show resolved
Hide resolved
Does this trick also work with now autogenerated new migrations or is there some manual adjustment needed afterwards before committing the migration files? |
If you change the method used for choices you will have to adjust it again. |
- Add custom migration class which handles errors
- Ensure that the new fields are added to the model
…t/InvenTree into refactor-states
…refactor-states
Hopefully the upstream fixes make the CI go through now |
@SchrodingersGat this would be ready for review and merge |
@matmair ok something screwy is going on:
Looks like we need to give this one some serious attention! |
Refactor for generic StatusCode definition. The goal is to make the code self-sufficient, 100% covered by unit tests and easy to use in any place needed (including plugins).
Specific changes: