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
It took me quite some time to realize that "*.csv" is used for the "path" instead of the "searchPattern" parameter and because of that, the interceptionCallback was not called when in the "C:"-directory a ".csv"-file was created.
Is there a way to prevent something like this from happening in the future? Maybe something like combining the "path" and "searchPattern" parameters into one?
The text was updated successfully, but these errors were encountered:
Thanks for reporting, @laurenzschmid. I implemented a change in #707 that replaces the two distinct filtering options with a single filter that uses a globbing syntax.
As this is a breaking change it will not be released immediately, as I have some other topics, I want to address before the next major release...
I wanted to get notified when a ".csv"-file is created and called the MockFileSystem.Intercept.Creating() method like this:
fileSystem.Intercept.Creating(
FileSystemTypes.File,
_ => throw customException,
"*.csv");
It took me quite some time to realize that "*.csv" is used for the "path" instead of the "searchPattern" parameter and because of that, the interceptionCallback was not called when in the "C:"-directory a ".csv"-file was created.
Is there a way to prevent something like this from happening in the future? Maybe something like combining the "path" and "searchPattern" parameters into one?
The text was updated successfully, but these errors were encountered: