v2.8.0
This commit is contained in:
parent
cdd01c6eac
commit
3074d4865b
3 changed files with 6 additions and 8 deletions
10
README.md
10
README.md
|
@ -1,4 +1,4 @@
|
|||
# jsx (v2.7.2) #
|
||||
# jsx (v2.8.0) #
|
||||
|
||||
|
||||
an erlang application for consuming, producing and manipulating [json][json].
|
||||
|
@ -120,7 +120,7 @@ false
|
|||
}">>
|
||||
```
|
||||
|
||||
#### to compile **jsx** so that it always decodes json objects to maps ####
|
||||
#### to compile **jsx** so that it always decodes json objects to maps ####
|
||||
|
||||
```bash
|
||||
$ JSX_FORCE_MAPS rebar3 compile
|
||||
|
@ -166,11 +166,9 @@ ignores bad escape sequences leaving them in strings unaltered
|
|||
if you're migrating from jsx v1.x to v2.x in most cases you won't need to
|
||||
make any changes to your code
|
||||
|
||||
support for encoding otp 17.0's new map type is now enabled by default when compiling
|
||||
support for otp 17.0's new map type is now enabled by default when compiling
|
||||
via rebar for any release that supports them. jsx should still compile cleanly for
|
||||
earlier releases without any user intervention. if you'd like to disable maps you can
|
||||
either set the env variable `JSX_NOMAPS` or by uncommenting the applicable tuple in
|
||||
`rebar.config`
|
||||
earlier releases without any user intervention
|
||||
|
||||
if you used any of `replaced_bad_utf8`, `single_quoted_strings`, `comments`,
|
||||
`ignored_bad_escapes` or `relax` you can simply omit them from your calls to jsx,
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue