-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Config] Support extensions without configuration in ConfigBuilder warmup #40859
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Config] Support extensions without configuration in ConfigBuilder warmup #40859
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you.
Did you get an exception thrown at you when warming the cache?
The goal is that no exceptions should be thrown in this stage. If you are trying to use a ConfigBuilder from your bundle (the one with no Configuration) only then you should get an exception.
Well done
@Nyholm yes, I did (an Error though):
|
Thank you <3 |
Did also get into this error when testing the beta with @sulu, @wouterj thx for fixing this 👍 . The |
It is fine to silently ignore it. You will get a proper extension if you are trying to use the config builder. |
Did see its just an info log not a warning or error log my eyes did play a prank on me 🙈. If we want still remove the log a PR is open: #41009 feel free to close. |
ConfigurationExtensionInterface::getConfiguration()
is nullable.As a real use-case: A small internal bundle in my company just uses
array_merge
to manage a very limited set of configuration. We don't have these fancy Configuration classes.