-
Notifications
You must be signed in to change notification settings - Fork 12
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
Implement import-export library #1081
Comments
The only places where importing might be nice to have is:
Exports might be nice at many places of course |
I've used it in a couple of my own projects and it works really well |
It appears to be more difficult than I thought upfront, because |
Let's close this, I don't really see us doing this if it is more complex than what we have already. |
I don't really agree. I do think it is a nice thing to do, as defining |
This library is awesome, would really make it easier to do some things that we have built manually |
I recently tried this out for a hobby project of mine and it works like a charm :) (at least, the exporting part. The importing part is a bit more tricky but luckily we don't use that) |
Describe the change
We could may be use https://django-import-export.readthedocs.io/en/latest/# for the importing (do we do that?) and exporting of information.
Motivation
We have a lot of duplicated csv exporting. And we have limited this to only what is necessary. With such a plugin exporting would become a breeze for all the data we have.
Current implementation
We have duplicated CSV exporting options everywhere.
Suggested implementation
Nice mixins.
Additional context
This issue should result in a new issue (possibly just change this one) that explains the benefits over just refactoring our current code. And if there are no benefits this issue is done and should be closed.
The text was updated successfully, but these errors were encountered: