dagger
dagger copied to clipboard
✨ `Stat` for `File`s and `Directory`s
What are you trying to do?
Inspect the state of a filesystem to check for the existence of expected files or directories.
Why is this important to you?
When writing a build for a specific project, this is less important, since you'll have specific expectations around what the filesystem looks like. But when writing code that aims to be reusable between projects, it's helpful to be able to examine the filesystem you're working with so that you can choose between different behaviors or give consumers useful error messages when they pass in a filesystem you can't work with.
How are you currently working around this?
My workaround is to create a container with the filesystem I want to examine, then call stat
inside the container.
I think @vito mentioned the plumbing is already in place.