By the way, I think using propertiesClassName to choose check logic in "cn/hippo4j/core/enable/BeforeCheckConfiguration.java" is not a good way. For instance, if the propertiesClassName is set to “SpringBootstrapConfigProperties” will do nothing.

@xjlgod Please resolve code conflicts.

@xjlgod Please resolve code conflicts.

I have done it. How about the question I talked.

Codecov Report

Patch coverage has no change and project coverage change: -0.09% ⚠️

Comparison is base (f1957dd) 34.53% compared to head (7e1ccea) 34.45%.
Report is 4 commits behind head on develop.

❗ Current head 7e1ccea differs from pull request most recent head 8c9e166. Consider uploading reports for the commit 8c9e166 to get more accurate results

@@              Coverage Diff              @@
##             develop    #1457      +/-   ##
=============================================
- Coverage      34.53%   34.45%   -0.09%     
  Complexity       846      846              
=============================================
  Files            262      262              
  Lines           5904     5918      +14     
  Branches         549      554       +5     
=============================================
  Hits            2039     2039              
- Misses          3672     3686      +14     
  Partials         193      193              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

By the way, I think using propertiesClassName to choose check logic in "cn/hippo4j/core/enable/BeforeCheckConfiguration.java" is not a good way. For instance, if the propertiesClassName is set to “SpringBootstrapConfigProperties” will do nothing.

If there are any problems with the current design, I will deal with them collectively.