-
-
Notifications
You must be signed in to change notification settings - Fork 551
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Update or remove non-ASCII test cases. #441
Labels
Comments
This was referenced Nov 6, 2016
The discussion is still open? isn't it? I think handling unicode where ever possible future proofs the solutions and improves the programming solutions. |
robkeim
added a commit
to robkeim/x-common
that referenced
this issue
Jan 30, 2017
rbasso
pushed a commit
to exercism/haskell
that referenced
this issue
Feb 1, 2017
rbasso
pushed a commit
to exercism/haskell
that referenced
this issue
Feb 1, 2017
rbasso
pushed a commit
to exercism/haskell
that referenced
this issue
Feb 1, 2017
behrtam
added a commit
to behrtam/python
that referenced
this issue
Mar 8, 2017
As discussed in exercism/problem-specifications#441 Fixes exercism#416
behrtam
added a commit
to exercism/python
that referenced
this issue
Mar 22, 2017
As discussed in exercism/problem-specifications#441 Fixes #416
emcoding
pushed a commit
that referenced
this issue
Nov 19, 2018
* Re-generate test file based on latest common test data. * Simplify test generator by using `number` value from canonical-data.json to determine test name.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
In #428 the decision was made to remove test cases containing non-ASCII characers from exercises that are not explicitly about extended character set handling.
The following tests were identified as containing test cases that need to be fixed:
Please check before removing a test that it is not also testing another property of the solution. If it is, please update the test to remove the non-ascii characters while maintaining the other intended purpose.
The text was updated successfully, but these errors were encountered: