Bug #109844 for Moo: Ambiguous error message when not providing "required" attributes

Sat Nov 28 04:40:00 2015 zhouzhen1 [...] gmail.com - Ticket created

Subject:	Ambiguous error message when not providing "required" attributes
Date:	Sat, 28 Nov 2015 17:39:43 +0800
To:	bug-Moo [...] rt.cpan.org
From:	Zhenyi Zhou <zhouzhen1 [...] gmail.com>

Hi, With latest Moo 2.000002, for a demo code like below, { package Foo; use Moo; has foo => (is => 'ro', required => 1); } my $foo = Foo->new(); It gives "Missing required arguments: foo at (eval 10) line 49." This error message is ambiguous and is not telling the the position of the exact problem. I wonder if we can improve this. Thanks!

Wed Mar 30 13:34:39 2016 CAZADOR [...] cpan.org - Correspondence added

I created a pull request here to fix this issue: https://github.com/moose/Moo/pull/25 On Sat Nov 28 04:40:00 2015, zhouzhen1@gmail.com wrote: Show quoted text

> Hi, > > With latest Moo 2.000002, for a demo code like below, > > { > package Foo; > use Moo; > has foo => (is => 'ro', required => 1); > } > > my $foo = Foo->new(); > > It gives "Missing required arguments: foo at (eval 10) line 49." > > This error message is ambiguous and is not telling the the position of the > exact problem. I wonder if we can improve this. Thanks!

Wed Mar 30 13:34:40 2016 The RT System itself - Status changed from 'new' to 'open'

Tue May 17 12:52:47 2016 haarg [...] haarg.org - Correspondence added

This is fixed in the repo.

Tue May 17 12:52:54 2016 haarg [...] haarg.org - Status changed from 'open' to 'patched'

Tue Jun 21 00:00:45 2016 haarg [...] haarg.org - Correspondence added

Fixed in 2.002002.

Tue Jun 21 00:00:45 2016 haarg [...] haarg.org - Status changed from 'patched' to 'resolved'