Closed nnseva closed 4 years ago
@nnseva: Thank you for the pull request. Actually I plan to refactor the supported-field logic. We probably don't need this kind of restriction, if we just check for subclasses of models.Field and exclude ForeignKeys and ManyToManyFields. All fields that are not a relation of any kind should return a value that makes sense as csv-column.
But for now your solution is fine.
Version 1.7 supports custom fields without the need to list them in the settings.
The supported field types list was restricted. This PR allows extending this list.