You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it seems that the option -cover_exclude only supports file patterns. This means that it is not possible to exclude a single file in a subfolder, say a/function1.m. if a file with the same name is also present in another subfolder, say a/b/c/function1.m. Indeed, the pattern function1.m would match both.
Would it be possible to support exclude filters which match the full path, such as a/function1.m? Meaning that this would only match. Maybe, a simple way to do this could be to treat patterns slightly differently if they contain the / chararcter : currently a pattern like a/function1.m of ./function1.m will never match anything, right?
The text was updated successfully, but these errors were encountered:
@jdbancal I think this is possible. I wonder if it would make sense to support something similar as rsync patterns, so that more complex patterns also involving directory names (maybe even including **) can be used.
For example, a utility function mocov_filename_matches_pattern could be added that compares whether a filename matches one or more patterns.
Before considering such an extensions: do you think this approach could work for your use case?
Currently it seems that the option
-cover_exclude
only supports file patterns. This means that it is not possible to exclude a single file in a subfolder, saya/function1.m
. if a file with the same name is also present in another subfolder, saya/b/c/function1.m
. Indeed, the patternfunction1.m
would match both.Would it be possible to support exclude filters which match the full path, such as
a/function1.m
? Meaning that this would only match. Maybe, a simple way to do this could be to treat patterns slightly differently if they contain the/
chararcter : currently a pattern likea/function1.m
of./function1.m
will never match anything, right?The text was updated successfully, but these errors were encountered: