If you want users to be able to pass file globbing patterns to your command, set a type of Globber
for the argument.
/**
* @path.hint file or directory to interact with.
**/
function run( required Globber path ) { }
Even though the user types a string, CommandBox will hand you a CFC instance that's preloaded with the matching paths and has some nice methods to help you interact with the matching paths. The Globber object lazy loads the matches, which gives you time to affect the pattern or even the sort if you wish prior to the file system actually being hit.
Use the count()
method to get the total number of paths matched on the file system.
function run( required Globber path ) {
print.line( path.count() & ' files affected!' );
}
The easiest way to apply some processing to each of the file paths found is by passing a closure to the apply()
method. The closure will be executed once for each result.
function run( required Globber path ) {
path.apply( function( thisPath ){
print.line( 'Processing file ' & thisPath );
} );
}
To get the raw results back, use the matches()
method.
If you want to get the results back as a query object, use the asQuery()
method and then you can loop over them yourself. The query contents match what comes back from directoryList()
.
function run( required Globber path ) {
var myQry = path
.asQuery()
.matches();
}
If you want to get the results back as an array, use the asArray()
method and then you can loop over them yourself.
function run( required Globber path ) {
var myArr = path
.asArray()
.matches();
}
Affect the order that the results come back by setting a sort. The sort follows the same pattern as the directoryList() function, which means it can be a comma-delimited list of columns to sort on.
function run( required Globber path ) {
var myQry = path
.asQuery()
.withSort( 'type, name' )
.matches();
}
To get the original globbing pattern that the user typed, use the getPattern()
method on the Globber CFC.
function run( required Globber path ) {
print.line( 'You typed ' & path.getPattern() );
}
You can create your own File Gobber object from any pattern using the globber()
method. You can pass a comma delimited list or an array of globber patterns to the constructor.
globber( 'models/**.cfc' ).matches()
globber( 'models/**.cfc,handlers/**.cfc' ).matches()
globber( [ 'models/**.cfc', 'handlers/**.cfc' ] ).matches()
You can also add additional glob patterns to an existing Globber object.
globber( 'models/**.cfc' )
.addPattern( 'handlers/**.cfc' )
.matches()
Sometimes when using a Globbing pattern, it's desirable to exclude a small number of patterns and it's cumbersome to manually include every pattern you want. You can set more than one excludes pattern to be passed to filter the matches. Excludes follow the same format as include patterns. If a pattern is both excluded and included, the exclude wins.
globber( '**.cf?' )
.setExcludePattern( '.git/,coldbox/' )
.matches()
Excludes, like includes, allow for a comma-delimited list or an array to be passed.
globber( '**.cf?' )
.setExcludePattern( [ '.git/', 'coldbox/' ] )
.matches()
The setExcludePattern()
method will override any existing methods, but the addExcludePattern()
method will add to the existing list.
globber( '**.cf?' )
.setExcludePattern( '.git/' )
.addExcludePattern( 'coldbox/' )
.matches()