This might be a cool thing to add to Fuse assumptions. (Assumptions are
simply cfparams that verify the variables in the Fusedoc are being
passed in)
My idea is that when creating a fuse you should add TWO sets of cfparams
instead of just one. One at the top of the file and one at the bottom.
The idea is that the fusecoder would put their code in between the "in"
and the "out" attributes. The "In Attributes" would verify that
attributes were passed into the fuse. The "Out Attributes" would verify
that attributes were created from within the fuse. Take a look:
<!---
|| BEGIN FUSEDOC ||
|| Properties ||
Name: act_insertusecase
Author: [EMAIL PROTECTED]
|| Responsibilities ||
I will insert a use case name into the FuseCad_usecases table
|| Attributes ||
-->attributes.application_id: an integer
-->attributes.usecase_name: a string
<--attributes.usecase_id: an integer
|| END FUSEDOC ||--->
<!--- in attributes --->
<cfparam name="attributes.application_id" type="numeric">
<cfparam name="attributes.usecase_name" type="string">
<!--- Code would go here --->
<!--- out attributes --->
<cfparam name="attributes.usecase_id" type="numeric">
Steve Nelson
Try my CFML code tester for free!
http://www.secretagents.com/tools/stomp/
(804) 825-6093
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
