You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test cases using checkPublicSuffix() take the domain and the expected privately registered domain as input but don't have any checks for what the public suffix of the domain is. In many cases this is just the privately registered domain minus the leading label. (Or all labels in the null case)
For a domain like .example.com which is expected to return null for the private domain, what is the expected "public suffix": null, example.com?
Is there any way that the test cases can be expanded to also include what the public suffix of a given domain should be?
The text was updated successfully, but these errors were encountered:
@sethmlarson Could you clarify what exactly you are trying to accomplish?
Afaiu .example.com is technically not a domain, plus our general stance is that the PSL is only a list and is up for interpretation (mostly because people cannot agree on what it should mean).
The test cases using
checkPublicSuffix()
take the domain and the expected privately registered domain as input but don't have any checks for what the public suffix of the domain is. In many cases this is just the privately registered domain minus the leading label. (Or all labels in thenull
case)For a domain like
.example.com
which is expected to returnnull
for the private domain, what is the expected "public suffix":null
,example.com
?Is there any way that the test cases can be expanded to also include what the public suffix of a given domain should be?
The text was updated successfully, but these errors were encountered: