getMetaData()allows us to parse the markup into something useful.
[category]tags categorise the function as appropriate, and the
@htmlpart describes the function’s parameter. The additional parameter data, such as whether it’s required, type and any defaults are automatically parsed too. This results in a display like:
Model.cfcis automatically included; if there’s no javaDoc comment, then they’ll appear in
uncategorized. But of course, there’s nothing stopping you creating your own
[category]tags, which will then automatically appear on the left hand column for filtering: you’re not restricted to what we’ve used in the core.
[section: Application]tag, with
[category: filters]. This way, your application documentation grows as you create it.
[section: Plugins]at the very least.
?reload=trueto see changes to your code. Additionally, Adobe ColdFusion is more aggressive in caching CFC metadata, so depending on your settings, you may not see changes until a server restart.
/global/functions.cfmfile. This is because we’re only looking at the main
Controller.cfcand what it can access.
show()to their respective routes too.