Re: [Pharo-dev] NeoCSV nil-Handling

Sean, > On 19 Feb 2018, at 02:33, Sean P. DeNigris wrote: > > Sven Van Caekenberghe-2 wrote >> What do you think ? > > Could #emptyFieldValue: accept a block instead of the actual value? Or be > per-field? Or both? Then the default could still be set via the current >

Re: [Pharo-dev] NeoCSV nil-Handling

Sven Van Caekenberghe-2 wrote > What do you think ? Could #emptyFieldValue: accept a block instead of the actual value? Or be per-field? Or both? Then the default could still be set via the current mechanism, keeping the usual API simple, but the user would have a bit more control. -

Re: [Pharo-dev] NeoCSV nil-Handling

Sean, > On 13 Feb 2018, at 14:39, Sean P. DeNigris wrote: > > I'd like a hook to specify default values more dynamically. The use case is > that I created a glue layer between Magritte and NeoCSV so one can > meta-describe how to extract CSV fields into objects. > > For

[Pharo-dev] NeoCSV nil-Handling

I'd like a hook to specify default values more dynamically. The use case is that I created a glue layer between Magritte and NeoCSV so one can meta-describe how to extract CSV fields into objects. For example: ``` descriptionDate ^ MADateDescription new