Is it possible to use shorter and thus better readable methodnames in JSON?

[JanSchankin]

Right now we sometimes have quite long and hard to read method names in the JSON-Files. This becomes tedious if the method names are slightly refactored, so that the names in the JSON files need to be changed too. If the change is not done together with the original refactoring but instead as part of a bugfix a few days later, or by another person that doesn't now anything about the refactoring, it becomes hard to find , or even notice the difference.

The names are this extensive, because they must be distinct. Maybe this can be circumnavigated by checking if the name already exists in the SampleRepository. If this is not the case a short name can be used. Otherwise the extensive distinct name must be used.

Is this possible?

[rcschrg]

When I remember correctly, there is an option to overwrite the method name with a custom string. I guess nobody will consistently implement it like this, when there is no way to force it, so this feature might be useless. Perhaps we should just add some kind of strict mode? This mode will check a. that all given names are unique and b. that the name was set. Back then i did intend that it should be the default mode to always name the method/pointcut/whatever yourself to avoid this refactoring problem.