Skip to content
This repository has been archived by the owner on Nov 6, 2018. It is now read-only.

Matcher returns wrong stems #144

Closed
reliak opened this issue Nov 24, 2015 · 3 comments
Closed

Matcher returns wrong stems #144

reliak opened this issue Nov 24, 2015 · 3 comments
Assignees
Milestone

Comments

@reliak
Copy link

reliak commented Nov 24, 2015

This addresses issue aspnet/Announcements#58

I have the following folder structure:

  • root
    • subfolder
      • sub1
      • sub2
      • sub3

I wanna find all files via:

var m = new Matcher();
m.AddInclude(@"**/*.*");
var res = m.Execute(new DirectoryInfoWrapper(new DirectoryInfo(root)));

As shown below, the Stems for files in sub2 and sub3 are wrong.
globissue

When I use a glob pattern starting with subfolder (see below) instead of the wildcards, all stems are correct:

var m = new Matcher();
m.AddInclude(@"subfolder/**/*.*");
var res = m.Execute(new DirectoryInfoWrapper(new DirectoryInfo(root)));

Update: Apparently the problem is not the glob pattern at the beginning. I inserted a folder under subfolder. When I now use the above pattern ("subfolder/**/*.*") I also get wrong stems.

/cc @anurse

@reliak reliak changed the title Matcher returns wrong stem when glob pattern starts with wildcard Matcher returns wrong stems Nov 24, 2015
@analogrelay
Copy link
Contributor

I think I've seen this before. @muratg we should work on this for RC2.

@muratg
Copy link

muratg commented Nov 24, 2015

Agreed!

@BrennanConroy
Copy link
Member

a6ffb85

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants