Select fields for export with BibTexWriter class

[andrejberg]

Now a list can be given of fields. Only those fields are returned in BibTexWriter is used to generate a string. This is not exactly what was asked in issue #195 but it should do the job.

[coveralls]

Coverage decreased (-0.05%) to 97.475% when pulling b653424b8cc2a4107ce099eb4e689cc229ba7841 on andrejberg:master into f6b480705598cf5baba09e73e46c8e509f41532f on sciunto-org:master.

[coveralls]

Coverage decreased (-0.05%) to 97.475% when pulling b653424b8cc2a4107ce099eb4e689cc229ba7841 on andrejberg:master into f6b480705598cf5baba09e73e46c8e509f41532f on sciunto-org:master.

[k4rtik]

Interested in this feature as well. Are there any reasons that it is still pending? cc: @sciunto

[MiWeiss]

Hi @andrejberg.

I just joined the project and wanted to give you a quick heads up.

In principle, I like the proposition. However, I am a bit worried that we're starting to overload the writer parameters. If we add this, it won't take long until we'll add an "exclude_fields" besides the here proposed "include_fields", and I see a range of other additions suggested in other issues. Maybe it would be more sustainable if we made this a bit bigger, and added the option to pass in customization functions, similar to the parsing.

I'll thus keep this open for just a bit longer, until a decision on the above was taken.

[MiWeiss]

Close as stale: No reaction to previous comments. Also, workaround easily implementable by just modifying the BibTeX database entries directly or by writing a simple customizer on parsing.