-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move some tests from toascii.json to urltestdata.json #38813
Conversation
These were introduced in e9a1061. However, these are not tests of the Unicode ToASCII algorithm. They are tests of the extra step introduced in whatwg/url@cceb435 to the URL Standard. Keep toascii.json focused on testing the ToASCII algorithm, so that software which implements it can use that file.
I agree with moving these tests from |
Now an idea came to mind: I think even better to move these tests to a new file, say /cc @annevk |
I think that might be reasonable, but I'm quickly reaching the limit of the extra effort I'm willing to put in here myself. I'm just trying to correct a bug so that my ToASCII library can be tested properly... |
}, | ||
{ | ||
"comment": "Empty host after domain to ASCII", | ||
"input": "https://\u00AD/", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add required base:
parameter, the same for remaining two tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall OK, you just skipped the required base:
parameter in the last three tests in the urltestdata.json
file.
These were introduced in e9a1061. However, these are not tests of the Unicode ToASCII algorithm. They are tests of the extra step introduced in whatwg/url@cceb435 to the URL Standard.
Keep toascii.json focused on testing the ToASCII algorithm, so that software which implements it can use that file.
/cc @rmisev