Closed dalehenrich closed 4 years ago
Originally reported as GsDevKit/GsDevKit_home#298 from @brunobuzzi ...
It seems there is bug in ChangeList>>parseSelector: (or Scanner>>scanMessageParts:) (tested on GS 3.5.1 & 3.5.4). Try:
ChangeList parseSelector: 'myMethodName -1 to: 2 do: [:i |].'.
But the following will work ok :
ChangeList parseSelector: 'myMethodName || -1 to: 2 do: [:i |].'.
So it seems a border case when you have a negative number immediately after the selector. The following also will fail:
ChangeList parseSelector: 'myMethodName -1 '.
The workaround will be add empty temp definition at the beginning "||" of the method.
As discussed here we should change MCFileTreeStCypressReader>>methodSelectorFor: to useRBParser >> parseMethodPattern:
MCFileTreeStCypressReader>>methodSelectorFor:
RBParser >> parseMethodPattern:
Originally reported as GsDevKit/GsDevKit_home#298 from @brunobuzzi ...
It seems there is bug in ChangeList>>parseSelector: (or Scanner>>scanMessageParts:) (tested on GS 3.5.1 & 3.5.4). Try:
ChangeList parseSelector: 'myMethodName -1 to: 2 do: [:i |].'.
But the following will work ok :
ChangeList parseSelector: 'myMethodName || -1 to: 2 do: [:i |].'.
So it seems a border case when you have a negative number immediately after the selector. The following also will fail:
ChangeList parseSelector: 'myMethodName -1 '.
The workaround will be add empty temp definition at the beginning "||" of the method.