Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support dynamic namespace filtering #40

Open
crisptrutski opened this issue Jan 6, 2016 · 0 comments
Open

Support dynamic namespace filtering #40

crisptrutski opened this issue Jan 6, 2016 · 0 comments

Comments

@crisptrutski
Copy link
Owner

Since doo-run-all can take a regex to limit the namespaces to run, in some cases it may be preferable to defer filtering namespaces to runtime - the holy grail of truth.

Since we need to enumerate the namespaces anyway currently to make sure they're loaded, in most cases this is not really worth it, but perhaps it makes the most sense in the case of using explicit .cljs.edn files (where the requires are known).

Currently this plugin plays-safe and subsets namespaces to test to those directly required by the edn file, but this would be an easy way out. Other possible cases could include files defining additional namespaces (through extra ns forms or magic macros?). Not sure if these are real cases.

Using an approach like this we could even collapse generic includes and excludes into a single (though eldritch) regex.

Just capturing this idea, but it may be nonsense.

Once doo supports filtering actual test cases, this exact problem comes back with a twist though, so no thought on it is wasted.

@crisptrutski crisptrutski changed the title Support dynamic namespace selection Support dynamic namespace filtering Jan 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant