A sample file beside a film is filed as a film #37
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
library_treeignores the directories upstream never resolves media out of(#25). It does not ignore the files upstream ignores, which are the rest of
Emby.Server.Implementations/Library/IgnorePatterns.cs:So a
sample.mkvbeside a film is a second film here, andsmall.jpgandalbumart.jpgare artwork upstream never offers a picture-naming rule.The globs are worth reading as what they are rather than as globs: upstream
works around its matcher having no repetition, so
sample.?throughsample.?????is "an extension of one to five characters". A port can say thatdirectly.
Not measured against a library yet — the reference one carries no samples. The
first step is to count what a real library holds, which upstream's own database
answers: rows whose path ends that way, and rows upstream filed that this one
would not.
Fixed and merged.
is_ignorednow covers upstream's file patterns as well as its directories:small.jpg,albumart.jpg,thumbs.db,*.bts,*.sync,*.trickplayandanything under one, every hidden name, the contents of a
sampleormintadirectory, and a sample file — written as "an extension of one to five
characters", which is what upstream's five globs are working around.
Checked against all 24 vectors from upstream's own
IgnorePatternsTests. Twoanswer differently and both are the same equivalence: upstream ignores the
intermediate directory at enumeration and never descends, so the resolved sets
match.
Artwork is untouched — the listing the picture rules read is the unfiltered
walk, as upstream's
LocalImageProviderreads a directory it does not runthese patterns over, so
albumart.jpgis still a music poster.Zero effect on the reference library: walking all of
/mnt/mediaunder the newrules ignores nothing, and none of the 14573 paths upstream filed would be
swallowed. The rules are scoped below the library root, so a library kept under
a dot directory still scans.