-
Notifications
You must be signed in to change notification settings - Fork 40.8k
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
Fix MustacheEnvironmentCollector to not ignore native fetcher #21060
Conversation
When the context is a map (as it is in a web View for instance) you can't assume a non-null fetcher actually contains the property you are searching for. This change alters the logic so that the native fetcher is always consulted if it exists, but there is always a fallback. Fixes spring-projectsgh-21045
CI failures look unrelated to me? |
Confirmed. The latest Micrometer 1.5 snapshots have broken our build. |
UPDATE: this patch is not complete. It fails to resolve |
I'm tempted to just apply this to 2.3.x rather than the older branches. Any objections @dsyer? |
No, I don’t think so. |
There is an unrelated change in |
I left it as a separate commit so you can leave it out easily if you want. |
Alter the logic of `MustacheEnvironmentCollector` so that the native fetcher is always consulted if it exists. When the context is a map (as it is in a web View for instance) you can't assume a non-null fetcher actually contains the property you are searching for. See gh-21060
Thanks @dsyer! I pulled the ignore commit out and applied it to 2.1.x onwards. The Mustache fix is just on 2.3.x+. |
When the context is a map (as it is in a web View for instance) you can't
assume a non-null fetcher actually contains the property you are searching
for. This change alters the logic so that the native fetcher is always
consulted if it exists, but there is always a fallback.
Fixes gh-21045