Value mismatch error when values seem to be the 'same' about tavern HOT 5 CLOSED

I'm guessing this is because it's an integer and user_id is being implicitly converted to an int at some point.

Because it might be desirable to actually have the distinction between an integer and a string being returned I'm not sure what the best thing to do is to fix this - it should at least print something more useful like

Value mismatch: '159295' (type: int) vs '159295' (type: str)

from tavern.

@michaelboulton This has been released right?

from tavern.

Currently, values from variables can only be passed by using string formatting (user_id: "{user_id}"). This loses any information about the original data type.

We should come up with another way of passing variables as they are. This might also be useful for passing whole json-blocks as data. String-formatting should stay as it has its own use case (e.g. Authorization header formatting).

Maybe a special token might be appropriate here. I am not sure which tokens are reserved in the yaml spec, so the symbol might need to be changed.

user_id: $user_id

from tavern.

This can be done using the yaml 'tags' (specs here http://www.yaml.org/spec/1.2/spec.html#id2803311) - for example:

request:
  json:
    user_id: !!int "{user_id_as_int:d}"

and custom tags can also be added (this is used for !include and !uuid).

It should be possible to make this 'pluggable' in future because it is just registering a function (eg

from tavern.

Using the default yaml tags does not work, unfortunately, because they are constructed before any string formatting is done.

I propose a solution involving an intermediate token which gets converted after string formatting is done. See #50 for my approach.

from tavern.