8 Nov
2011
8 Nov
'11
8:55 a.m.
On Nov 7, 2011, at 11:46 PM, Tudor Girba wrote:
Hi,
This is not the cleanest part of Moose :).
the code quality is nice but the comment ratio is zero and this is the problem. As we
learn and understand we will comment.
If I understand correctly, you would like to specify a new Operator to be run at the end
of the default ImportingTask. There is no mechanism for that, because we never had the use
case.
The closest thing for is the way to run the CandidateOperator. Take a look at
MooseCompositeImporterTask. At the end of basicRun, the candidateOperator is run if it is
present.
Yes I will do that and improve the comments.
And may be add a importer to be run after importing.
It would probably be interesting to have some more
extensibility here. But, what is your use case?
Two simple cases
- I want to attach author information that I collect from Smalltalk but the sister
importer will be that I get an author DB in Java and that I want to connect it to a
model.
The idea is to have a reusable class that I can plug or not in the importer phase.
- I want to build a map showing the number of committed version in a pharo repository.
Again I want to automatically run it when I want it.