4.x: Config metadata docs #7581
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oracle-contributor-agreement
bot
added
the
OCA Verified
romain-grecourt
previously approved these changes
Sep 13, 2023
…to documented types.
- remove references that no longer exist - replace old configured types with new ones - fix modules that did not generate config metadata
tomas-langer
force-pushed
the
config-metadata-docs
branch
from
48bd482
to
184cf2e
Compare
|
Rebased on latest |
romain-grecourt
approved these changes
Sep 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Resolves #5659
Update to all configured types, including the generated documentation.
Updated pom files that were missing processor configuration
Documentation
Removed types that no longer exist
Added new configured types
Re-generated configuration documentation in
docs/configDecision
This PR fails to build as existing documentation references non-existent configuration types. As I cannot fix this in the docs, we have to decide how to continue: