Spring-starter configuration file keyword prompt

[totalo]

According to #13449. @ZjcNB and I would like to discuss this issue.

There are currently two ways to achieve
The first one is that we pay attention to the key prefix, and we cannot prompt the user for the subsequent nested classes, for example:
spring.shardingsphere.rules.sharding.sharding-algorithms.databaseShardingAlgorithm.type=INLINE
keyword.customvalue.customvalue=customvalue

and the keyword is spring.shardingsphere.rules.sharding.sharding-algorithms.

Second, we pay attention to the complete key, but there will be a problem that the key of props cannot identify the red flag (the solution to this problem is still being sought), for example
spring.shardingsphere.rules.sharding.sharding-algorithms.databaseShardingAlgorithm.type=INLINE
keyword.customvalue.keyword=customvalue

and the first keyword is spring.shardingsphere.rules.sharding.sharding-algorithms and the second is type.

Custom values cannot be recognized and reminded by idea, keywords can be reminded.

[totalo]

hi ,@terrymanu @tristaZero Regarding the two, which method should we be more appropriate?

[zhaojinchao95]

@totalo Hi, let’s continue to investigate, so that it can automatically prompt and there is no red warning