Unexpected Folder Structure of Instrumented Files

[marcusellis05]

Not sure this is an issue outright or unexpected behavior on my part.

My node files are grouped into folders for controllers, routes, models, etc. The folder structure looks something like this:

lib/

• controllers/
• models/
• routes/
• services/

When I run the Grunt task, I expect to see a new folder "lib-cov" with the same list of folders underneath it. Instead I get:

lib-cov/

• lib/
  • • controllers/
  • • models/
  • • routes/
  • • services/

Is this the correct behavior? Seems that the additional depth is unnecessary and I'm wondering if I've done something wrong. My task config looks like this:

blanket: {
  instrument: {
    files: {
      'lib-cov/': ['lib/**/*.js']
    }
  }
}

Thanks.

[alex-seville]

Your understanding is correct. This is a flaw I haven't yet corrected. Sorry, I expect to fix it this week.

[marcusellis05]

No worries. I've got a workaround in place in the meantime. Thanks.

[alex-seville]

Fixed. The syntax in the gruntfile has changed though. You only need to specify the directory.

blanket: {
  instrument: {
    files: {
      'lib-cov/': ['lib/']
    }
  }
}

.js files will automatically be detected and parsed.