Registry config javadoc #16015
Registry config javadoc #16015
Conversation
quarkus-bot
bot
added
area/devtools
aloubyansky
force-pushed
the
registry-config-javadoc
branch
from
3c5aa5a to
68a9396
Compare
| * the client will not send requests to resolve platform extension catalogs to the registry. | ||
| * | ||
| * @return true if the registry will be able to handle platform descriptor requests, otherwise - false | ||
| */ | ||
| Boolean getExtensionCatalogsIncluded(); |
There was a problem hiding this comment.
Why this method is not returning a primitive?
There was a problem hiding this comment.
The way it is implemented currently, the default config is provided by the registry itself. The client may have a customized version of it (i.e. by selectively overriding some values) in the config.yaml. When the registry client is initialized, it is merging the default registry config and the client side version (if it exists). A non-null value from this method would represent a user's choice, which will override the registry's default. So null in this case will mean that the user is willing to accept whatever the registry's default is.
There was a problem hiding this comment.
I'd recommend to put that in the Javadoc, but too late now :)
Added missing javadoc.