DTO，VO等用于方法名时的问题 #4
Assignees
Labels
enhancement
New feature or request
Comments
|
从规范描述来看这个应该是错误的，提示的是方法名，方法名应该是要满足驼峰要求的 |
|
涉及到规范的，建议还是去阿里官方那边提问吧，我这边只是基于他提供的pmd规则进行检查的idea插件 |
好的好的，感谢回复 |
|
翻了一下阿里那边的issue，发现官方目前没解决，不知能否内置几个常用的 |
|
是这样的，官方似乎也是这样建议的
…________________________________
From: Jack Chu ***@***.***>
Sent: Monday, August 21, 2023 6:59 PM
To: godfather1103/p3c ***@***.***>
Cc: MashiroT ***@***.***>; Mention ***@***.***>
Subject: Re: [godfather1103/p3c] DTO，VO等用于方法名时的问题 (Issue #4)
@mashirot<https://github.com/mashirot> 你是说按照alibaba/p3c#556的说法增加SPI的引入是吗？<https://github.com/alibaba/p3c/issues/556%E7%9A%84%E8%AF%B4%E6%B3%95%E5%A2%9E%E5%8A%A0SPI%E7%9A%84%E5%BC%95%E5%85%A5%E6%98%AF%E5%90%97%EF%BC%9F>
―
Reply to this email directly, view it on GitHub<#4 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMOVRL4G4ZCLNAR6U4ZLNRTXWM5RVANCNFSM6AAAAAA3YFAZ7Q>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
font{
line-height: 1.6;
}
ul,ol{
padding-left: 20px;
list-style-position: inside;
}
周末有时间的话，我再看看，如果我后面增加对其支持的话，会重新打开该issue
Jack Chu
***@***.***
…---- 回复的原邮件 ----
发件人
***@***.***>
发送日期
2023年08月21日 19:22
收件人
***@***.***>
抄送人
Jack ***@***.***>
,
State ***@***.***>
主题
Re: [godfather1103/p3c] DTO，VO等用于方法名时的问题 (Issue #4)
是这样的，官方似乎也是这样建议的
________________________________
From: Jack Chu ***@***.***>
Sent: Monday, August 21, 2023 6:59 PM
To: godfather1103/p3c ***@***.***>
Cc: MashiroT ***@***.***>; Mention ***@***.***>
Subject: Re: [godfather1103/p3c] DTO，VO等用于方法名时的问题 (Issue #4)
@mashirot<https://github.com/mashirot> 你是说按照alibaba/p3c#556的说法增加SPI的引入是吗？<https://github.com/alibaba/p3c/issues/556%E7%9A%84%E8%AF%B4%E6%B3%95%E5%A2%9E%E5%8A%A0SPI%E7%9A%84%E5%BC%95%E5%85%A5%E6%98%AF%E5%90%97%EF%BC%9F>
―
Reply to this email directly, view it on GitHub<#4 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMOVRL4G4ZCLNAR6U4ZLNRTXWM5RVANCNFSM6AAAAAA3YFAZ7Q>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
|
好的
…________________________________
From: Jack Chu ***@***.***>
Sent: Monday, August 21, 2023 7:33 PM
To: godfather1103/p3c ***@***.***>
Cc: MashiroT ***@***.***>; Mention ***@***.***>
Subject: Re: [godfather1103/p3c] DTO，VO等用于方法名时的问题 (Issue #4)
font{
line-height: 1.6;
}
ul,ol{
padding-left: 20px;
list-style-position: inside;
}
周末有时间的话，我再看看，如果我后面增加对其支持的话，会重新打开该issue
Jack Chu
***@***.***
---- 回复的原邮件 ----
发件人
***@***.***>
发送日期
2023年08月21日 19:22
收件人
***@***.***>
抄送人
Jack ***@***.***>
,
State ***@***.***>
主题
Re: [godfather1103/p3c] DTO，VO等用于方法名时的问题 (Issue #4)
是这样的，官方似乎也是这样建议的
________________________________
From: Jack Chu ***@***.***>
Sent: Monday, August 21, 2023 6:59 PM
To: godfather1103/p3c ***@***.***>
Cc: MashiroT ***@***.***>; Mention ***@***.***>
Subject: Re: [godfather1103/p3c] DTO，VO等用于方法名时的问题 (Issue #4)
@mashirot<https://github.com/mashirot> 你是说按照alibaba/p3c#556的说法增加SPI的引入是吗？<https://github.com/alibaba/p3c/issues/556%E7%9A%84%E8%AF%B4%E6%B3%95%E5%A2%9E%E5%8A%A0SPI%E7%9A%84%E5%BC%95%E5%85%A5%E6%98%AF%E5%90%97%EF%BC%9F>
D
Reply to this email directly, view it on GitHub<#4 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMOVRL4G4ZCLNAR6U4ZLNRTXWM5RVANCNFSM6AAAAAA3YFAZ7Q>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
―Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>
―
Reply to this email directly, view it on GitHub<#4 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMOVRL63QS77CV57KPNAOZDXWNBPVANCNFSM6AAAAAA3YFAZ7Q>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@mashirot 我准备增加配置窗口用于自己添加对应的内容
|
|
@mashirot 你截图的规则报错是LowerCamelCaseVariableNamingRule规则造成的，但是我看对应规则实现类中并没有获取过对应namelist.properties文件中的配置项，只能考虑在对应代码中的正则表达式上做文章了 |
|
|
@mashirot https://github.com/godfather1103/p3c/releases/tag/1.3-2023.2-2.1.1 |
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
不知道我对规约的理解是否有误，但这样命名应该是正确的，不应该提示？
The text was updated successfully, but these errors were encountered: