I'm currently fixing issues with my code while running integration tests on an EC2 instance of a Windows machine. Despite resolving the filenames-are-too-long problem, several paths remain unresolved due to being hardcoded for UNIX systems.
I've been exploring nodejs' Path module but I'm unsure about what changes are needed to ensure the path names work correctly on both operating systems (aside from changing backslashes). Do I need to prefix these path names for Windows?
Below is a snippet of the code that's causing the issue:
function getDirectories(srcpath) {
//srcPath looks like graph-validator/tests/data/graph-examples/
return fs.readdirSync(srcpath).filter(function(file) {
return (
file !== '.git' && fs.statSync(path.join(srcpath, file)).isDirectory()
)
})
}
const dataDirectory = 'graph-validator/tests/data/'
// Generate valid input for included minimal tests
function createDatasetFileList(path) {
const testDatasetPath = `${dataDirectory}${path}`
//path is often 'graph-examples/ds001/'
if (!isNode) {
return createFileList(testDatasetPath)
} else {
return testDatasetPath
// testDatasetPath = graph-validator/tests/data/graph-examples/ds001/
}
}
I experimented with path.join() and it helped partially solve the issue, especially with the slashes. How can I ensure that these path names work seamlessly across different operating systems?