Glob patterns for tsp compile target on windows

[p-bakker]

When I run tsp to compile .tsp files and I want to compile all .tsp files in a specific folder I use ./some folder/*.tsp

This works fine on MacOS, but not on Windows

Shouldn't tsp internally deal with glob patterns?

[timotheeguerin]

Guess I didn't even think that ever worked(on unix either), in what context do you do that?

[p-bakker]

An NPM script like tsp compile ./specs/public/*.tsp --config tspconfig.yaml in my package.json, run through npm run somescriptname

[timotheeguerin]

tsp compile only will take a single entrypoint which must be a file, are you sure it was actually building everything here? are the other files not imported from the first one?

trying to repro that locally I get an error (on osx) saying it doesn't know what that 2nd file is

Unknown argument: ./scratch/specs/public/b.tsp

[p-bakker]

Looks like you're right... If I put multiple .tsp files into ./specs/public/ and specify ./specs/public/*.tsp as the path param for tsp compile, it errors out...

If I just have 1 .tsp file in ./specs/public/ and I specify ./specs/public/*.tsp as the path param for tsp compile, it DOES compile that one .tsp file in the folder, even if its not called main.tsp. This gave me a false sense that glob patterns did work, but it looks like they don't

You think a feature request for this would be considered, or?

[timotheeguerin]

What is the goal to have this? Compile multiple fiels independently or import them all together?

The problem with supporting glob pattern here is that we do want at some point to allow url imports and this will break that usage.