Skip Menu |

This queue is for tickets about the Test-Warnings CPAN distribution.

Report information
The Basics
Id: 127106
Status: open
Priority: 0/
Queue: Test-Warnings
People
Owner: Nobody in particular
Requestors: PETDANCE [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Wishlist
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Thu Sep 13 12:02:08 2018 PETDANCE [...] cpan.org - Ticket created
Subject: Add a function for allow_warnings { block }
I've recently switch to Test::Warnings from Test::NoWarnings, and now I'm doing search & destroy on tests that throw warnings. It would be nice if I could do something like: allow_warnings_in_this_block { code(); code(); code(); }; I've been doing: allow_warnings(1); code();code();code(); allow_warnings(0); or my $ignore = warnings { code(); code(); }; and neither is very satisfying.
  Sat Sep 15 21:22:00 2018 ether [...] cpan.org - Severity Normal changed to Wishlist
  Tue Oct 30 14:59:09 2018 ether [...] cpan.org - Correspondence added
Show quoted text
> It would be nice if I could do something like: > > allow_warnings_in_this_block { > code(); code(); code(); > };
I just ran into such a usecase myself today. I ended up doing this: warnings(sub { ... stuff that might generate warnings ... }); So I think a allow_warnings(&) or warnings_ok(&) would probably just be an alias to the current 'warnings' sub. It would be nicer to have this though (as you suggested in the other ticket): allow_warnings([ qr/.../, ...], sub { ... });
  Tue Oct 30 14:59:09 2018 The RT System itself - Status changed from 'new' to 'open'
  Tue Oct 30 16:07:39 2018 PETDANCE [...] cpan.org - Correspondence added
Show quoted text
> I just ran into such a usecase myself today. I ended up doing this: > > warnings(sub { > ... stuff that might generate warnings ... > });
So you're just capturing the warnings and then ignoring them? Kinda sneaky, but not obvious. An alias for clarity would be good.