Check that deprecation replacement property exists in additional-spring-configuration-metadata.json

Question

Check that deprecation replacement property exists in additional-spring-configuration-metadata.json

Opened this issue 3 days ago · 2 comments

It's possible to specify a non-existent property in the "deprecation"."replacement" field. I think it should be possible to validate that the referenced property exists.

Answer 1 · 2025-11-06T10:37:02.000Z

This might be tricky on main when the replacement may be in a different module but should be easier in the 3.x branches.

Answer 2 · 2025-11-06T11:45:02.000Z

This could happen at the spring-boot-docs level when we generate the appendix or something? Even in 3.x, I don't think we should validate the replacement with a partial view of the world.