Exclusion pattern doesn't work (the .kavitaignore replacement)

[janaxhell]

What happened?

According to the wiki

**/folder/* will ignore the folder at any depth in a path

I have many series folders that contain an /Extra subfolder with HTML presentation full of gifs/jpegs and such. With .kavitaignore I used Extra/* and all seemed to work fine. Now I have tried the same pattern in the UI, but it doesn't work, so I tried the above example as **/Extra/*
and it doesn't work as well. I have manually removed the bogus "series", rescanned with that exclusion and they came back.
My hierarchy is
/comics/country/publisher/series/Extra
with all the .cbz files at the same level of /Extra in
/comics/country/publisher/series/

I'm using latest 0.8.4.0

What did you expect?

To not see bogus series thumbnails appear among legit series.
I.e I have a real series folder called "L'Eternauta" inside which there is a subfolder called /Extra, containing HTML presentation
In the UI I now see a legit "L'Eternauta" entry with the first issue cover thumbnail and a second "L'Eternauta" entry showing a random pic from the HTML content inside /Extra.
With .kavitaignore I could filter that out.

Kavita Version Number - If you don not see your version number listed, please update Kavita and see if your issue still persists.

0.8.4 - Stable

What operating system is Kavita being hosted from?

Docker (Other)

If the issue is being seen on Desktop, what OS are you running where you see the issue?

None

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Other (List in "Additional Notes" box)

If the issue is being seen on Mobile, what OS are you running where you see the issue?

None

If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on?

No response

Relevant log output

No response

Additional Notes

No response

[majora2007]

I was able to reproduce this. I do see a few potential points of failure:

1. The matcher was missing on some flows when scanning for files/folders
2. There may be some mismatch with slashes that I need to handle better