fix: skip top domain when cookie is disabled #580
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.
Summary
For test cookie, we have the random id each time when testing whether the cookie is enabled in the browser, this might introduce too many cookies if the remove operation gets any issue. Following the TS SDK, think we can just use the general key for testing purpose.
With
disabledCookies
set totrue
, we still have atopDomain
function which still uses the cookies (base-cookie
):getLocation
andgetHost
to utils, so we can mock/stub the functions, otherwise aswindow.location
is not writable/configurable, we cannot unit test the features, also moving these two standalone functions into utils for better readability.topDomain
inMetadataStorage
when cookies is disabled.Checklist