Fix support for nested options.customOptionsPath
#4491
Merged
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.
Fixes #PROD-1243
Description Of Changes
When testing PROD-1243 (from #4462) I found that I could cause
Fides.init(...)
to crash by supplying a nestedoptions.customOptionsPath
that didn't exist, e.g.This throws an error like:
Code Changes
consent-banner-tcf.cy.ts
consent-utils.test.ts
getWindowObjFromPath
to be defensive when descending nested pathsSteps to Confirm
Pre-Merge Checklist
CHANGELOG.md