why do you need the filename though?

nice, at Nubank we had some crashes in prod related to use schema.core/with-fn-validation in a production code 😅 , so we are thinking on add a custom lint for that function to check if the filename contains a src (usually, at least for our services, production code)

and emit a warning/error to avoid that code go to prod

so you would like to discourage with-fn-validation within certain namespaces?

not namespaces, because we can't know only by a ns if that's is from test source-path

I think we would need the filename or file uri

Wouldn't that just be something for: https://github.com/clj-kondo/clj-kondo/blob/master/doc/linters.md#discouraged-var

Damm, didn't know about this one, sounds perfect

will take a look, thank you very much

Actually, we do use it on tests, using that would make the warn for tests as well right? :/

yes, but you can make an ns-group for your tests (e.g. all namespaces ending with -test ) and then undo it for the tests

got it, sounds good

will test it, thanks!

the ns-group :pattern is a pattern for the ns right? I think that won't work since we can't know if a ns is a test, for example test/my_service/foo/my_feature.clj (`(ns my-service.foo.my-feature)`)

it's a common convention to name test nses foo_test.clj

but maybe could also enable a regex based on the file. gotta go now

yeah I know, but we have some integration legacy tests not using that convention, I think it'd be convenient to have a file-pattern optional, WDYT?

@U04V15CAJ WDYT? would you accept a issue about it? I can try to find some time to implement the file-pattern support if you want

issue welcome, + PR

https://github.com/clj-kondo/clj-kondo/issues/1790