You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before 0.005, it was possible to ignore the class slot of the spec, as long as a pre-built object was set in App::Spec::Run::cmd.
Now, op method names are assumed to be fully-qualified, and if not, they're prefixed with the class. I'm not sure why this is.
The text was updated successfully, but these errors were encountered:
Ok, I had a quick look into the code handling the classname, it looks broken.
I'll have a look, but I can't promise a fix for the next major release, because I want to get a release out tomorrow with my recent fixes.
Thanks for the report =)
Before 0.005, it was possible to ignore the
class
slot of the spec, as long as a pre-built object was set inApp::Spec::Run::cmd
.Now, op method names are assumed to be fully-qualified, and if not, they're prefixed with the class. I'm not sure why this is.
The text was updated successfully, but these errors were encountered: