cucumber-expressions: {word}-expression with unicode fix - #471
Conversation
…ICODE_CHARACTER_CLASS flag soles this problem.
| for (String chunk : chunks) { | ||
| chunk = chunk.trim(); | ||
| data.add(chunk.split("\n")); | ||
| data.add(chunk.split(System.lineSeparator())); |
There was a problem hiding this comment.
Please ensure the examples.txt file has unix line endings and this shouldn't be needed.
There was a problem hiding this comment.
Looks good - I’ll merge this when the other implementations have a similar fix.
There was a problem hiding this comment.
@mpkorstanje, I use Windows as default OS. And I've faced a problem when tried to run tests that were in your repo. I think Files.readAllBytes(Path p) adds line separator depending on the OS that it's executed on.
So I can't use unix line endings if I use Windows. I guess, it won't be convenient for other users too.
There was a problem hiding this comment.
@aslakhellesoy, I don't really understand what exactly do you mean by "other implementations".
There was a problem hiding this comment.
JavaScript, Go and Ruby
|
Hi @savkk, Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾 In return for this generous offer we hope you will:
On behalf of the Cucumber core team, |
|
This broke cucumber on Android because of |
|
Although this flag exists in Android and docs says that it has no effect on Android but can be passed it is omitted in source code and passing it throws exception. |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
Details
I think the summary is detailed enough :)
Motivation and Context
I have a problem when using {word}-expression with russian words.
How Has This Been Tested?
I've written unit-tests. An I'm testing it in my bdd-project.
Types of changes
Checklist: