-
-
Notifications
You must be signed in to change notification settings - Fork 785
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
v4 add custom delimiter for csv. #1814
Comments
django-import-export is based on tablib. I had a quick look at the tablib source to see how they handle custom delimiters, and it doesn't look to me that it is directly configurable, although it seems there is some code to detect delimiter. Perhaps if you created a subclass of a data format it would be possible. You'd have to read their docs and source to find out. django-import-export doesn't allow for custom delimiters at present, but we could maybe support it if it was implemented in tablib. |
hi. from what i found it seems configurable in tablib:
source: https://tablib.readthedocs.io/en/stable/formats.html |
Ah yes, looks like you can do it in tablib, although we don't support it in django-import-export. I guess it could be configurable. This would be the starting point. |
yes. simple example below:
in order to support one delimiter this code is fine. for example by moving the delimiter value to settings. |
and with working imports:
and then it looks like some more definition work is needed for various formats on each field if one moves to csv, but also this is configurable by defining each field appropriately in resources ? |
Hello, v4 has reduced the amount of dependencies of libs. In order to profit optimally I want to try to move to csv only. However I am missing the spot how I can customize the delimiter and or support multiple different delimiters in version v4. Ideally the correct separator is automatically detected based on the language the user has and something the user can override during import or export.
The text was updated successfully, but these errors were encountered: