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
Currently EpBehaviorCategoryChange and ClassRecategorized have the name of the old and new categories, and the class that is categorized. From this information it is not possible to know the old package of the class.
For example, below we move the class WrapperSignal from the tag Signals in the package Beacon-Core to the tag Signals in the package Beacon-Extra.
From the Epicea event we can get the name of the new package and new category so we can determine the package name and the tag name. But we only get the name of the previous category, Beacon-Core-Signals in this case, and based on it we do not know what the package/tag names are.
Fixing this would require extending all the places that raise ClassRecategorized announcements to also save the old package name.
Tested in Pharo-11.0.0+build.383.sha.421dbef721c2c2bf771fab5c999a9a0260225096 (64 Bit)
The text was updated successfully, but these errors were encountered:
Currently
EpBehaviorCategoryChange
andClassRecategorized
have the name of the old and new categories, and the class that is categorized. From this information it is not possible to know the old package of the class.For example, below we move the class
WrapperSignal
from the tagSignals
in the packageBeacon-Core
to the tagSignals
in the packageBeacon-Extra
.From the Epicea event we can get the name of the new package and new category so we can determine the package name and the tag name. But we only get the name of the previous category,
Beacon-Core-Signals
in this case, and based on it we do not know what the package/tag names are.Fixing this would require extending all the places that raise
ClassRecategorized
announcements to also save the old package name.Tested in Pharo-11.0.0+build.383.sha.421dbef721c2c2bf771fab5c999a9a0260225096 (64 Bit)
The text was updated successfully, but these errors were encountered: