[Agavi-Tickets] [Agavi] #1453: Allow validators to specify result code for exported data

2 views

Skip to first unread message

Agavi

unread,

Nov 16, 2011, 2:59:00 AM11/16/11

to tic...@lists.agavi.org

#1453: Allow validators to specify result code for exported data
-------------------------+--------------------------------------------------
Reporter: david | Owner: dominik
Type: enhancement | Status: new
Priority: normal | Milestone: 1.1
Component: validation | Version:
Severity: normal | Keywords:
Has_patch: 0 |
-------------------------+--------------------------------------------------
Right now, anything that gets {{{export()}}}ed is set as
{{{AgaviValidator::SUCCESS}}}, so it must not be validated again. But with
#1419, people may want to export, say, an {{{AgaviUploadedFile}}} to the
"files" source based on a filename parameter read from "parameters", and
require this file to be validated separately.

A third argument to {{{AgaviValidator::export()}}} should accept the
status code and default to {{{AgaviValidator::SUCCESS}}}.

--
Ticket URL: <http://trac.agavi.org/ticket/1453>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5

_______________________________________________
Agavi Tickets Mailing List
tic...@lists.agavi.org
http://lists.agavi.org/mailman/listinfo/tickets

Agavi

unread,

Nov 16, 2011, 3:02:38 AM11/16/11

to tic...@lists.agavi.org

#1453: Allow validators to specify result code for exported data
-------------------------+--------------------------------------------------
Reporter: david | Owner: dominik

Type: enhancement | Status: closed

Priority: normal | Milestone: 1.1
Component: validation | Version:

Severity: normal | Resolution: fixed
Keywords: | Has_patch: 0
-------------------------+--------------------------------------------------
Changes (by david):

* status: new => closed
* resolution: => fixed

Comment:

(In [4872]) Allow validators to specify result code for exported data,
closes #1453