fix: to prevent spell checking errors when a user home directory has …

[benjam-es]

What:

• Bug Fix

Description:

When running the test suite locally, my home directory is atum which is seen as a mis-spelling. As we usaully exclude that part of the directory elsewhere, this issue only arrises on the constant check within the Cache class.

To prevent this, we ensure that the project path is inferred within the class to match other code, and we also ignore those words that are found within the project directory base path.

Added in a similar way to presets

Related:

[benjam-es]

@nunomaduro @c0nst4ntin #95 is an alternative approach to fixing the test suite locally without ignoring words, although I believe this approach is more useful as general users might have use DIR within constants in their projects

[benjam-es]

@c0nst4ntin can this be the first issue and #95 be the duplicate? as I say - I think this has more benefit

[c0nst4ntin]

Sure. Both solutions can work. I will change the labels and leave the decision to Nuno

[c0nst4ntin]

Hey @benjam-es , I took another look at this. Sorry for the delay. Generally, I like the idea, as the project name might sometimes also be very specific, so this would be ignored automatically as well.
 

1. I am unsure if the use case you mentioned at the top is still required. 
   I believe Nuno stopped checking the constant values in 4f81fc4

2. Maybe you could also write a test for the new functionality checking if the isWordIgnored() returns true for parts of the project path.

3. I am a bit unsure about this, as it might introduce inconsistent behaviour on different machines, as the project folder might be called differently. For example, your username might be ignored because of your path. Then if you use it in a doc block, it would not fail. For other developers or on the CI, it would fail because the path is different.