perl-CELL / Tickets / #39 Provide a more concise way to construct status objects

#39 Provide a more concise way to construct status objects

Milestone: Alpha

Status: closed

Owner: Smith Farm

Labels: None

Updated: 2014-06-02

Created: 2014-05-25

Creator: Smith Farm

Private: No

ATM status objects must be constructed verbosely by calling App::CELL::Status->new( ... ) -- think about alternative ways to construct status objects. For example, the $CELL singleton could be used like this:

$status = $CELL->status_info( 'FOOBAR_MESSAGE', args => [ ... ] );
return $CELL->status_err( 'FOO_ERROR_45534', args => [ ... ] );

Discussion

Description has changed:

Diff:

--- old
+++ new
@@ -1,6 +1,6 @@
-$status->code returns code string, but it could also be run as App::CELL::Status->code( 'FOOBAR_MESSAGE', level => 'info' ) which would mean less typing.
+ATM status objects must be constructed verbosely by calling App::CELL::Status->new( ... ) -- think about alternative ways to construct status objects. For example, the $CELL singleton could be used like this:

-Another idea would be to use the $CELL singleton like so: 
+   $status = $CELL->status_info( 'FOOBAR_MESSAGE', args => [ ... ] );
+   return $CELL->status_err( 'FOO_ERROR_45534', args => [ ... ] );

-   $CELL->status( 'FOOBAR_MESSAGE', 'info', args => [ ... ] );

status: open --> closed

Smith Farm - 2014-06-02

as of 0.154 we have a "constructor factory" in CELL.pm that makes status_$level functions so we can do, e.g.

return $CELL->status_err( 'FOO_ERROR' ); return $CELL->status_warn( 'FOO_WARNING' );
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Provide a more concise way to construct status objects

Configuration, Error-handling, Localization and Logging

Milestone

Searches

Help

#39 Provide a more concise way to construct status objects

Discussion