1. 统一包名修改
This commit is contained in:
@@ -22,7 +22,7 @@ import java.util.List;
|
||||
@AutoConfiguration
|
||||
@ConditionalOnClass(LoginUser.class)
|
||||
@ConditionalOnBean(value = {CompanyDataPermissionRuleCustomizer.class, DeptDataPermissionRuleCustomizer.class})
|
||||
public class CloudBusinessDataPermissionAutoConfiguration {
|
||||
public class ZtBusinessDataPermissionAutoConfiguration {
|
||||
|
||||
@Bean
|
||||
public CompanyDataPermissionRule companyDataPermissionRule(List<CompanyDataPermissionRuleCustomizer> customizers) {
|
||||
@@ -19,7 +19,7 @@ import java.util.List;
|
||||
* @author ZT
|
||||
*/
|
||||
@AutoConfiguration
|
||||
public class CloudDataPermissionAutoConfiguration {
|
||||
public class ZtDataPermissionAutoConfiguration {
|
||||
|
||||
@Bean
|
||||
public DataPermissionRuleFactory dataPermissionRuleFactory(List<DataPermissionRule> rules) {
|
||||
@@ -16,7 +16,7 @@ import static com.zt.plat.framework.common.enums.WebFilterOrderEnum.TENANT_CONTE
|
||||
*/
|
||||
@AutoConfiguration
|
||||
@ConditionalOnClass(name = "feign.RequestInterceptor")
|
||||
public class CloudDataPermissionRpcAutoConfiguration {
|
||||
public class ZtDataPermissionRpcAutoConfiguration {
|
||||
|
||||
@Bean
|
||||
public DataPermissionRequestInterceptor dataPermissionRequestInterceptor() {
|
||||
@@ -21,7 +21,7 @@ import java.util.List;
|
||||
@AutoConfiguration
|
||||
@ConditionalOnClass(LoginUser.class)
|
||||
@ConditionalOnBean(value = {PermissionCommonApi.class, DeptDataPermissionRuleCustomizer.class})
|
||||
public class CloudDeptDataPermissionAutoConfiguration {
|
||||
public class ZtDeptDataPermissionAutoConfiguration {
|
||||
|
||||
@Bean
|
||||
public DeptDataPermissionRule deptDataPermissionRule(PermissionCommonApi permissionApi, List<DeptDataPermissionRuleCustomizer> customizers) {
|
||||
@@ -43,7 +43,7 @@ import static java.util.Collections.singletonList;
|
||||
* 注意,使用 DeptDataPermissionRule 时,需要保证表中有 dept_id 部门编号的字段,可自定义。
|
||||
*
|
||||
* 实际业务场景下,会存在一个经典的问题?当用户修改部门时,冗余的 dept_id 是否需要修改?
|
||||
* 1. 一般情况下,dept_id 不进行修改,则会导致用户看不到之前的数据。【cloud-server 采用该方案】
|
||||
* 1. 一般情况下,dept_id 不进行修改,则会导致用户看不到之前的数据。【zt-server 采用该方案】
|
||||
* 2. 部分情况下,希望该用户还是能看到之前的数据,则有两种方式解决:【需要你改造该 DeptDataPermissionRule 的实现代码】
|
||||
* 1)编写洗数据的脚本,将 dept_id 修改成新部门的编号;【建议】
|
||||
* 最终过滤条件是 WHERE dept_id = ?
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
com.zt.plat.framework.datapermission.config.CloudDataPermissionAutoConfiguration
|
||||
com.zt.plat.framework.datapermission.config.CloudDeptDataPermissionAutoConfiguration
|
||||
com.zt.plat.framework.datapermission.config.CloudBusinessDataPermissionAutoConfiguration
|
||||
com.zt.plat.framework.datapermission.config.CloudDataPermissionRpcAutoConfiguration
|
||||
com.zt.plat.framework.datapermission.config.ZtDataPermissionAutoConfiguration
|
||||
com.zt.plat.framework.datapermission.config.ZtDeptDataPermissionAutoConfiguration
|
||||
com.zt.plat.framework.datapermission.config.ZtBusinessDataPermissionAutoConfiguration
|
||||
com.zt.plat.framework.datapermission.config.ZtDataPermissionRpcAutoConfiguration
|
||||
|
||||
Reference in New Issue
Block a user