Futilities/v0.6/clade/Sys/dba/InReq: Difference between revisions
< Futilities | v0.6 | clade | Sys | dba
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
|- | |- | ||
| align=right | | | align=right | | ||
[WFe]{{l/ver/clade|p=Ferreteria|Sys\Data | [WFe]{{l/ver/clade|p=Ferreteria|Sys\Data\Engine\aux\is|RqActor}} [t]<br> | ||
(base){{l/ver/clade/base|InReq}} | (base){{l/ver/clade/base|InReq}} | ||
| → {{l/ver/clade|Sys\dba|InReq}} | | → {{l/ver/clade|Sys\dba|InReq}} | ||
Revision as of 14:31, 25 September 2025
| Clade Family | ||
|---|---|---|
| → InReq |
→ DoExport | |
Purpose
Each object encapsulates a given input (request) term. Podling-clades will implement actions and provide functions to access needed values from the input, which is encapsulated by a cInRqData object which can be retrieved from function OAUserInput().
To make use of additional user arguments (after the first), InputRq podlings (aka InReq podlings) can implement function ParseInputArgs(array $ar).
Doing Stuff
- To access input arguments, get an appropriate cInRqData object:
$this->OAUserInput()returns the raw input value strings (split but not parsed), one element for each term in the user input