-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ProxyEntityAvailable 接口继承问题 #220
Comments
@lzl1030152809 您好请问是否可以发一下您现在的代码,因为正常情况下这个接口是无法做到继承的除非父类也不确定具体类型才可以 |
public abstract class BaseModel<TEntity, TProxy extends ProxyEntity<TProxy, TEntity>> implements ProxyEntityAvailable<TEntity, TProxy> { |
@lzl1030152809 您先在子类手动实现一下我下个版本修复:) |
@xuejmnet 好的 |
@lzl1030152809 主要这个接口实现可以通过插件快速实现所以没考虑到这个情况 |
xuejmnet
added a commit
that referenced
this issue
May 25, 2024
xuejmnet
added a commit
that referenced
this issue
May 25, 2024
xuejmnet
added a commit
that referenced
this issue
May 25, 2024
@lzl1030152809 2.0.19已经修复 |
@xuejmnet 好的 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
父类实现 ProxyEntityAvailable 接口,子类不继承时会报错 is not implements ProxyEntityAvailable
![image](https://private-user-images.githubusercontent.com/20924956/333796404-6cfcf252-3cff-4f9a-9ba5-1b42a15d4069.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk4MDM2NTcsIm5iZiI6MTcxOTgwMzM1NywicGF0aCI6Ii8yMDkyNDk1Ni8zMzM3OTY0MDQtNmNmY2YyNTItM2NmZi00ZjlhLTliYTUtMWI0MmExNWQ0MDY5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzAxVDAzMDkxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTVkMGQzZDA1MWI3Y2U0MDYxMTZiMzY3Nzg1YzI3MmZhOTYzNjMxZDk1MjU3MjEyZmZjYTA1YTdiZjcwZGVmYTUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.B9JDg9suEP3YRmgcnxpgkZCXiapZqvci2Kk5kdS1ej0)
只找了子类实现的接口,未找父类实现的接口
The text was updated successfully, but these errors were encountered: