Skip to main content

ColdFusion Tip: How to tell if path is file or directory

Today, one of the ColdFusion users asked me a question "Is there anyway I can find out whether a path is a directory or a file? There is no isDirectory() function available in ColdFusion and I don't want to write Java code to do this. Any help?"
For a moment I thought really! is there no way that ColdFusion can tell you whether a given path is of a directory or file? But sooner, I came across the function 'getFileInfo' which takes the path as an argument and returns a struct data that contains various metadata properties of the file. The struct includes a key - 'type' whose value can either be a directory or file. The below code shows how you can determine whether the given path is of a directory or file:

<cfset fileInfo = getFileInfo(expandPath("./myDir")) > <cfif fileInfo.type EQ "directory"> <!--- is a directory ---> <cfelseif fileInfo.type EQ "file"> <!--- is a file ---> </cfif> <cfdump var="#fileInfo#">

The other metadata properties such as canRead, canWrite, isHidden, lastModified, parent, size included in the resultant struct can also come handy.

Comments

  1. Could probably just use DirectoryExists() as well. I believe that would return false if it's a regular file.

    ReplyDelete
    Replies
    1. @Matt,
      DirectoryExists() is a nice function, but it is used to check whether a directory\path exists. It would return true only when the given directory is found and would return false if not found.

      <cfoutput>#directoryExists(expandPath("./dirExists"))#</cfoutput> <!--- returns true\yes --->
      <cfoutput>#directoryExists(expandPath("./dirDoesntExist"))#</cfoutput> <!--- returns false\no --->

      Of course, it would return false if you mention a file name, but assuming that it returns false only for the file names wouldn't be right.

      On the other hand getFileInfo() gives you the right data(file\directory).

      Delete
    2. Matt is assuming you know the resource exists and simply want to discover it's type.

      If you don't know whether it exists and need to know the type (i.e. extra info is irrelevant), you can just do DirectoryExists and FileExists in combo:







      Of course, it's also worth pointing out that if you've done a cfdirectory you've already got this info available from the query returned by that (and from CF8 onwards can filter it with the type attribute).

      Delete
    3. It's 2012 and there's *still* buggy blog software incapable of handling angle brackets. :/

      Here's what the gap in the middle of the above comment should be:

      <cffunction name="getPathType" output="false" returntype="string">
      <cfargument name="Path" type="String" required />
      <cfreturn DirectoryExists( Arguments.Path )
      ? "dir"
      : FileExists( Arguments.Path )
      ? "file"
      : ""
      />
      </cffunction>

      Delete
    4. @Peter,
      You're right, that's another way of doing it. However, I find getFileInfo('path').type as an easy way to determine whether the resource is a file or directory. If an assumption is made that the resource exists then DirectoryExists() would suffice. I wouldn't use two functions to determine the resource type.

      Delete
  2. Nice tip, Sagar. I use GetFileInfo quite a lot, but never thought to apply it to a directory.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to use the APP_INITIALIZER token to hook into the Angular bootstrap process

I've been building applications using Angular as a framework of choice for more than a year and this post is not about another React vs Angular or the quirks of each framework. Honestly, I like Angular and every day I discover something new which makes development easier and makes me look like a guy who built something very complex in a matter of hours which would've taken a long time to put the correct architecture in place if I had chosen a different framework. The first thing that I learned in Angular is the use of the APP_INITIALIZER token.

Using MobX to manage application state in a React application

I have been writing applications using React and Redux for quite some time now and thought of trying other state management solutions out there. It's not that I have faced any issues with Redux; however, I wanted to explore other approaches to state management. I recently came across MobX  and thought of giving it a try. The library uses the premise of  `Observables` to tie the application state with the view layer (React). It's also an implementation of the Flux pattern wherein it uses multiple stores to save the application state; each store referring to a particular entity. Redux, on the other hand, uses a single store with top-level state variables referring to various entities.

De-obfuscating javascript code in Chrome Developer Tools

I had blogged about JavaScript debugging with Chrome Developer Tools  some time back, wherein I have explained how these developer tools can help in debugging javascript code. Today Google Chrome 12 was released and my Chrome browser was updated to this version. As with every release, there have been some improvements made on performance, usability etc,. One feature that stood out for me is the ability to De-obfuscate the javascript code. What is Minification? Minification is the process of removing unnecessary characters such as white spaces, comments, new lines from the source code. These otherwise would be added to make the code more readable. Minifying the source code helps in reducing the file size and thereby reducing the time taken to download the file. This is the reason why most of the popular javascript libraries such as jQuery are minified. A minified jQuery file is of 31 KB in size where as an uncompressed one is about 229 KB. Unfortunately, debugging minified javascript f...