-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
Support for Log4Perl #1412
Comments
There are no plain definitions of methods you've specified. They are all introduced using perl magick. Such kind of magick i s not yet supported. |
I feared something like that. |
Nono, don't close. may be sometime. |
Wow, great. Thank you! I didn't believe for a solution after 2 years. |
Hey, I'm trying to use it now, but I still get
on all my log statements.
am I doing something wrong? I'm using version 2019.3. |
Hey, thanks for checking :-) I have those:
So Log4perl seems to be installed for this Perl (right?). In the settings, I just switched my Target Version to 5.28, too, but that didn't change anything: Looking at your screenshot, it seems like your If that's of relevance, I'm using PyCharm 2019.3.1. |
Okay, I read both pages before but wasn't really able to see where Log4perl fits in there. Is it that it is a Is there anything I can do except disabling the inspection altogether? |
Can't check myself atm, but its one of:
|
First: Geat thanks for this wonderful plugin. It's reallly the best perl-pluging of all IDEs I've ever seen.
I'm heavily use the Log::Log4perl logging framework in my projects. But the methods are not proper supported by Camelcade.
1)The type of the returned object (Log::Log4perl::Logger) from the exported function get_logger() ist not regognized. I have to prefix ist manually (like line 6)
2) The exported sub "get_logger" ist marked by:
"Unable to find sub definition, declaration, constant definition or typeglob aliasing less... (Strg+F1) "
in line 6
3) If I type $logger->.. (line 8) a lot of methods are suggested, but not the most used logging-methods: debug, info, warn, fatal.
4) The debug() - method itself is also remarked with the "Unable to find sub definition..."
Is it possible to fix it?
Here is a screenshot:
The text was updated successfully, but these errors were encountered: