--extend-exclude doesn't work with absolute paths

[ember91]

I hope this hasn't been reported before.

typos version: 1.23.6

/some/path/some_misspellings.txt is a file with errors which typos in its default configuration would detect.

/some/path/_typos.toml has the contents:

[files]
extend-exclude = [
    '/some_misspellings.txt'
]

This works as expected, i.e. no errors are reported:

cd /some/path/
typos --force-exclude some_misspellings.txt

Although this reports spelling errors:

cd /some/path/
typos --force-exclude /some/path/some_misspellings.txt

I assumed that they would lead to the same result.

[epage]

extend-exclude makes paths relative to a "base directory", using gitignore syntax. So /some_misspellings.txt says that some_misspellings.txt should only be excluded if its in the root directory.

So the question is what is the root in this case. From a quick glance, it looks like its ".". It should probably be the parent directory of the config file. We are tracking this in #593.

Whatever the root is, we should make sure that a passed in path is checked against the root, regardless of format.

[ember91]

Just to lessen any confusion: Removing the initial slash from extend-exclude leads to the same behavior as with a slash.

[epage]

Now, that is surprising.