4.x: Fixed configuration metadata of blueprints that are configured and provide a service #8891
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.
Updated generated documentation to latest state of code.
Resolves #8776
There were two problems in the code:
@Option.Provider(ProtocolConfigProvider.class)
in listener config)After fixing the above problems, the generated documentation correctly shows the configuration keys, and the listener config documentation now lists all available implementations.
In addition the same problem was with observe providers. Fixed all providers to add config key, re-generated the documentation.
Added validation that
@Provides
and@Configured
must have a configuration key.