-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
QF-2700 Run makemigrations --check right after building #675
Conversation
Task linked: QF-2700 Run migrations check in CI |
56ab5cc
to
0a1a3a7
Compare
Thank you, I am not able to comment on the arm-wrestling approach, but I believe the libqfieldsync changes are not needed in here? |
By default my editor completely hide changes to submodules. I had fixed this but a fresh reset brought the defaults back. Sorry |
No worries, I think we should change that to a pypi package instead. |
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
Interesting that the code had to be refactored like this, thanks for winning the wrestling contest!
I think it opens the discussion to retire the Geodb
module once again.
b4da829
to
d463f90
Compare
* Removed libqfieldsync changes * fixed by removing staticmethod * Removed libqfieldsync changes
What looked like adding a single line of code turned into me arm-wrestling the Django migration writer.
The issue is basically that the migration writer doesn't know how to serialize bound functions -- functions parameterized with an implicit reference -- and that static methods seem to be considered as bound functions.
I went for the "brutal" way of solving this: i.e. extracting the static method to a top-level function. There are other ways. Please make a commit suggestion if you are not happy with the way I went for.