deanlaw / cfcgenerator

Automatically exported from code.google.com/p/cfcgenerator
8 stars 6 forks source link

Request for custom component prefix #43

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Fill in details
2. Generate code

What is the expected output? What do you see instead?
The generated filenames use the final directory in the CFC path as the
filename prefix. The issue is that, often the final directory is named
'com' or 'cfc' so you end up with com.cfc, comDAO.cfc, etc.  It would be
helpful if there were an optional field where the user could specify their
own component prefix that would be used instead of the last directory name.

What version of the product are you using? On what operating system?
cfcgenerator_build_7_2007-06-01 / WinXP Pro

Original issue reported on code.google.com by rabidgad...@gmail.com on 11 Jun 2007 at 12:36

GoogleCodeExporter commented 9 years ago
I just noticed that, contrary to what I originally thought, there doesn't seem 
to be
a generated filename. The app is just tacking an extension on to the end of the
directory structure. I'm guessing this is an oversight since previous versions 
of the
PU36 appended the table name as the filename prefix. It seems to have been left 
out
in this release. 

Original comment by rabidgad...@gmail.com on 11 Jun 2007 at 12:43

GoogleCodeExporter commented 9 years ago
the prefix goes in the path name

Original comment by brian.ri...@gmail.com on 11 Jun 2007 at 1:17