You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes I'd like to create a new instance of my recordClass with some additional initializations. Say I need to create a new empty address in a Customer Address on import. So I'd like the CSVREader not only to create a new instance by sending #new to the class, but something else.
I see two or three scenarios for this:
we add an inst var #creationMethod (with a default of #new)to NeoCSVReader and send that method to the #recordClass in #readNextRecordAsObject
ex: myReader creationMethod: #newWithEmptyAddress
we add an inst var #postCreationMethod and send it to the newly created instance after its creation
we add some Block for this purpose
First question: does this make sense at all?
Second question: I have never used Pharo with Iceberg and git before and have no real idea hwo to do it, but if I wanted to, what version of Pharo and NeoCSVReader should I use these days? Pharo 8 or 9?
Here is what I think #readNextRecordAsObject would look like with this change:
Sometimes I'd like to create a new instance of my recordClass with some additional initializations. Say I need to create a new empty address in a Customer Address on import. So I'd like the CSVREader not only to create a new instance by sending #new to the class, but something else.
I see two or three scenarios for this:
#new
)to NeoCSVReader and send that method to the #recordClass in #readNextRecordAsObjectex:
myReader creationMethod: #newWithEmptyAddress
First question: does this make sense at all?
Second question: I have never used Pharo with Iceberg and git before and have no real idea hwo to do it, but if I wanted to, what version of Pharo and NeoCSVReader should I use these days? Pharo 8 or 9?
Here is what I think #readNextRecordAsObject would look like with this change:
``readNextRecordAsObject
...
``
The text was updated successfully, but these errors were encountered: