Support spaces in filenames

[youhavethewrong]

It would be nice to be able to have spaces in filenames, for example:

POST http://localhost:8000
Content-type: text/plain
file, ../../Text file test.txt;

This currently produces a parse error:

error: Parsing literal
  --> example.hurl:3:18
   |
 3 | file, ../../Text file test.txt;
   |                  ^ expecting ';'
   |

[youhavethewrong]

I've opened PR #288 to support this behavior.

[fabricereix]

It's a good idea to support space in filename.
But I think that they should be escaped as in the terminal, because they are not enclosed within quotes.

$ ls space\ in\ filename.txt 
'space in filename.txt'

You example would become:

POST http://localhost:8000
Content-type: text/plain
file, ../../Text\ file\ test.txt;

[youhavethewrong]

I see your point, but doesn't the semi-colon function as the end-of-filename delimiter, rendering the backslashes unnecessary?

[fabricereix]

There is also the whitespace issue.
Whitespace can be added/removed without changing the content.

the following lines all use the same file 'myfile':

file, myfile;  # leading space (recommended)
file, myfile ; # unnecessay trailing space
file,myfile;   # missing leading space

[youhavethewrong]

I'm happy to update my PR with additional capabilities. If I add the ability to escape spaces via backslash (\) should I allow any character to be escaped, similarly to shell?

[fabricereix]

Yes, you can update your PR.
We can first focus on the space, and deals with other escaping later on, with a different Issue/PR.