Skip to content
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 debug logs in ConfigProxyFactory #670

Closed
wants to merge 1 commit into from
Closed

Conversation

kilink
Copy link
Member

@kilink kilink commented Aug 31, 2023

Fix debug logs in createInterfaceProperty / createScalarProperty to actually log the relevant types, instead of always logging "Class" and "Proxy".

Fix debug logs in createInterfaceProperty / createScalarProperty to actually log
the relevant types, instead of always logging "Class" and "Proxy".
@@ -377,13 +376,13 @@ private static <T> Function<Object[], T> createDefaultMethodSupplier(Method meth
};
}

protected <T> MethodInvoker<T> createInterfaceProperty(String propName, final T proxy) {
LOG.debug("Creating interface property `{}` for type `{}`", propName, proxy.getClass());
protected <T> MethodInvoker<T> createInterfaceProperty(String propName, final T proxy, Class<?> targetClass) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, basically, this method exists just so that 1) we have a neat place to log, and 2) the internal API remains symmetrical with scalar and parametrized properties?
I'm not objecting, just making sure I'm getting it :-)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh... actually now that I see it's a protected method, I likely shouldn't change the signature at all. I can move the logging outside of the method I suppose.

@kilink kilink closed this Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants