Skip to content

feat: fix up sending of string types#7

Merged
untitaker merged 3 commits into
masterfrom
string-repr-vars
Jul 20, 2018
Merged

feat: fix up sending of string types#7
untitaker merged 3 commits into
masterfrom
string-repr-vars

Conversation

@untitaker

Copy link
Copy Markdown
Member

No description provided.

@untitaker
untitaker requested a review from mitsuhiko July 20, 2018 12:16
@untitaker

Copy link
Copy Markdown
Member Author

As far as I understood it's desirable to always send the repr for any string type in vars, not the string itself.

@mitsuhiko

Copy link
Copy Markdown
Contributor

@untitaker I would even go as far as proposing to send any value that is not a list/dict as repr'ed string. For instance one could make the argument that integers and bools are fine just like this, but in reality even this is wrong. For instance Python shows bools as True/False but javascript as true/false. Likewise integers over 53bit do not survive in JSON on the way to the browser so long ints are also preferrably string.

@mitsuhiko mitsuhiko left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm other than the broken test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants