Julian Verdurmen
Julian Verdurmen
With Reqnroll 3 you could fix this with the ExpressionType parameter, see https://docs.reqnroll.net/latest/automation/cucumber-expressions.html#explicit-expression-type-control So closing this as fixed :)
Could someone create a repo for this? Then I will look for a fix
Is the only difference with and without BOM? They all are UTF8? Also curious, how did you do the check?
> Related to [#718](https://github.com/reqnroll/Reqnroll/issues/718)? I think just coincidence. Or I missed it's character encoding week 😆
@gasparnagy should we really label this a bug?
What is not valid in your opinion? The BOM of UTF8 is optional. Some editors write it, others don't. And ASCII is a subset of UTF8 (without BOM). I think...
I have ran a Bash script to get the encodings of all files, it's using `file -i` It checked all the files (1682) and found 6 files with UTF16LE. Reqnroll/Formatters/ExecutionTracking/PickleExecutionTracker.cs...
See https://github.com/reqnroll/Reqnroll/pull/729 for the fix of the 6 files.
~This looks like the solution~ ~working-tree-encoding in .gitattributes~ ~https://git-scm.com/docs/gitattributes#_working_tree_encoding~ update: nope, that is the encoding in your working tree, so local. Not in the repo
> Somehow my VisualStudio editor was configured for UTF-16. Was this a test for https://github.com/reqnroll/Reqnroll/issues/718? 👼