YCM Jason
YCM Jason
Maybe I didn't do a good job describing the issue. Please allow me to clarify: When putting the glob pattern in `test:unit`, `deno task test:unit` will run all matched paths....
> Maybe I'm misunderstanding what you're trying to do. By default you want to have `deno task test:unit` execute all unit tests, but if you do `deno task test:unit path/to/test.ts`...
@bartlomieju > I can see usefulness of this solution, but I'm not yet sure how we could tackle that without breaking existing workflows. I understand there might be constraints I'm...
The solution I have in my mind is to use `--include` for the glob and free args for the target. For example ```bash # find all files based on src/**/*.test.ts...
With the above, we could define the deno task as ``` "test": "deno test --include=\"src/**/*.test.ts\"" ``` Then `deno task test` would run `deno test --include=\"src/**/*.test.ts\"`, all files matching `src/**/*.test.ts` would...
@iuioiua I am curious to understand about specifying modules. I understand that we want to keep things trim, but wouldn't tree shaking handle that for us?
@iuioiua rebased and resolved conflicts!
Created a PR #8698 to fix the types.
@mikehardy please count me in!
I do think a combination of both ideas can be a good idea. I like #12763 proposal for allowing more structured way of defining permission, and I also like this...