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

Getting "The type is unrecognized" if spaces are added #125

Open
khmarochos opened this issue Mar 29, 2016 · 1 comment
Open

Getting "The type is unrecognized" if spaces are added #125

khmarochos opened this issue Mar 29, 2016 · 1 comment

Comments

@khmarochos
Copy link

Hello,

First of all, thank you very much for your contribution. I found it about a half of a year ago, but now I can't imagine Perl5-development without using the Method::Signatures module.

I'd like to show you something and, I believe, you'll find it interesting. Sometimes I need use something like that:

method some_method(
    HashRef                 $some_hashref,
    XML::LibXML::Node       $some_xml_libxml_node,
    Bool                    $some_bool
) { ... }

In some of these cases I get the following error message:

In call to Some::Module::some_method(), the type XML::LibXML::Node       is unrecognized (perhaps you forgot to load it?)

If I remove spaces between XML::LibXML::Node and the parameter's name, everything's fine, but, of course, it would be nice to have these spaces where they are :)

Would you be so kind as to look at this issue when you have some time?

Thank you!

@barefootcoder
Copy link
Contributor

Thanks for the report! As I'm sure you've noticed, few of us have had the chance to devote much time to Method::Signatures as of late. However, I did just now take a quick look at your issue. My initial, naive attempt to reproduce the problem (i.e. by adding some spaces at the end of the class test in t/type_check.t) didn't recreate your error. I wonder if you might have some time to try to produce a failing test that we could turn into a unit test? I can't guarantee that will result in a fix, but it's definitely got a lot more potential to do so. :-)

Sorry for the long delay in replying.

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

No branches or pull requests

2 participants