fix(Node): Fix error and crash due to custom cacheFolder in achecker.yml #1240
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Code to address the case when a user configures a custom cacheFolder in achecker.yml.
The problem was, the previous code did not account for the fact that the code runs in the accessibility_checker/src/lib folder, so a require( ) has to be relative to this directory, hence the need to go up two directory levels if the cacheFolder is relative path and not a fully qualified path.
This update works for any cacheFolder directory.
This PR is related to the following issue(s):
#1149
Additional information can be found here:
Testing reference:
In order to test, edit cacheFolder in achecker.yml (as shown in the lines below) to any desired directory, then run automated test to verify there are no failures.
I have conducted the following for this PR: