Skip to content

Conversation

@ephraimbuddy
Copy link
Contributor

The previous_name and version_renamed fields were added to the configuration section to track the previous name and the version in which it was renamed for a given configuration option.

This also helps us retain the version-added value of config options when the config section is renamed.

This information of rename is also made available in the config documentation

Closes: #28076

@uranusjr
Copy link
Member

Instead of adding a bunch of ~, would it be simpler to omit them and use get('previous_name') instead?

I also wonder if it’s better to do

renamed:
  previous_name: ...
  version: ...

so it’s clearer the two keys must appear together.

@ephraimbuddy ephraimbuddy force-pushed the recorgnize_section_rename branch from d767b3d to 9161add Compare December 13, 2022 08:27
This helps us retain the version added value of config options when
the config section is renamed.
This information of rename is also made available in the config documentation
@ephraimbuddy ephraimbuddy force-pushed the recorgnize_section_rename branch from 9161add to 964afea Compare December 13, 2022 15:13
@ephraimbuddy ephraimbuddy merged commit 9e58795 into apache:main Dec 14, 2022
@ephraimbuddy ephraimbuddy deleted the recorgnize_section_rename branch December 14, 2022 07:51
@ephraimbuddy ephraimbuddy added the type:improvement Changelog: Improvements label Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants