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
Suppose you have a base ITransformer class with a subclass for each type:
public abstract class BaseTransformer<T> implements ITransformer<T>
├─ public class ClassTransformer extends BaseTransformer<ClassNode>
├─ public class MethodTransformer extends BaseTransformer<MethodNode>
└─ public class FieldTransformer extends BaseTransformer<FieldNode>
Modlauncher expects the interface to be implemented in the transformer class itself.
Therefore running this structure will result in an exception.
The text was updated successfully, but these errors were encountered:
arguably, this is a trivial fix in the code: implement on the class itself, rather than the parent. It's a bit untidier but would result in functional code.
Suppose you have a base
ITransformer
class with a subclass for each type:public abstract class BaseTransformer<T> implements ITransformer<T>
├─
public class ClassTransformer extends BaseTransformer<ClassNode>
├─
public class MethodTransformer extends BaseTransformer<MethodNode>
└─
public class FieldTransformer extends BaseTransformer<FieldNode>
Modlauncher expects the interface to be implemented in the transformer class itself.
Therefore running this structure will result in an exception.
The text was updated successfully, but these errors were encountered: