ReAbstractRule class >> #ruleName is #subclassResponsibility and should be implemented by slime rules. Otherwise stack traces like the following keep popping up.
The other option would be to implement #ruleName along side #name on the instance side.
GRBasicNewInitializeMissingRule class(Object)>>subclassResponsibility
GRBasicNewInitializeMissingRule class(ReAbstractRule class)>>ruleName
GRBasicNewInitializeMissingRule(ReAbstractRule)>>ruleName
ReTrivialCritique(ReAbstractCritique)>>title
ReTrivialCritique class(ReProperty class)>>convertToCalypsoBrowserItem:
ReTrivialCritique(Object)>>asCalypsoBrowserItem
[ ] in UndefinedObject(ClyQueryResultBrowserAdapter)>>wrapRawItems:startingAt:
OrderedCollection>>collect:
ClyQueryResultBrowserAdapter>>wrapRawItems:startingAt:
ClyQueryResultBrowserAdapter>>itemsStartingAt:count:
ClyBrowserQueryCache>>fillItemsFrom:
ClyBrowserQueryCache class>>filledBy:startingAt:size:
ClyQueryResultBrowserAdapter>>createUpdateWithItemsStartingAt:count:
ClyBrowserQueryCache>>createFullUpdateOf:
ClyBrowserQueryCursor>>updateItemCache
ClyCollapsedDataSource(ClyDataSource)>>runUpdate
[ ] in UndefinedObject(ClyDataSourceUpdateScheduler)>>runUpdateFor:
OrderedCollection>>do:
[ ] in ClyDataSourceUpdateScheduler>>runUpdateFor:
WorldState>>runStepMethodsIn:
WorldMorph>>runStepMethods
WorldState>>doOneCycleFor:
WorldMorph>>doOneCycleNow
WorldMorph>>doOneCycle
[ ] in WorldMorph class>>doOneCycle
FullBlockClosure(BlockClosure)>>ensure:
WorldState class>>doDrawCycleWith:
WorldMorph class>>doOneCycle
MorphicRenderLoop>>doOneCycle
MorphicRenderLoop>>doOneCycleWhile:
[ ] in UndefinedObject(MorphicUIManager)>>spawnNewProcess
[ ] in CleanBlockClosure(BlockClosure)>>newProcess
The situation in Pharo 9 is like this
ReAbstractRule >> #name
self subclassResponsibility
The situation in Pharo 14 is like this
ReAbstractRule >> #name
^ self ruleName
ReAbstractRule >> #ruleName
^ self class ruleName
ReAbstractRule class >> #ruleName
^ self subclassResponsibility
The change was introduced in Pharo 13 with the change in ReAbstractCritique >> #title
pharo-project/pharo@713dd1d#diff-c24507e47816f0ee3e1a676fa54f74c8b40cd50d6314b984c4b89a1936ae22b1R213
ReAbstractRule class >> #ruleNameis#subclassResponsibilityand should be implemented by slime rules. Otherwise stack traces like the following keep popping up.The other option would be to implement
#ruleNamealong side#nameon the instance side.The situation in Pharo 9 is like this
The situation in Pharo 14 is like this
The change was introduced in Pharo 13 with the change in
ReAbstractCritique >> #titlepharo-project/pharo@713dd1d#diff-c24507e47816f0ee3e1a676fa54f74c8b40cd50d6314b984c4b89a1936ae22b1R213