All Versions
21
Latest Version
Avg Release Cycle
117 days
Latest Release
-

Changelog History
Page 2

  • v1.7.0 Changes

    September 25, 2018

    2018-09-24

    • New: EnumJsonAdapter makes it easy to specify a fallback value for unknown enum constants. By default Moshi throws an JsonDataException if it reads an unknown enum constant. With this you can specify a fallback value or null.
       new Moshi.Builder()
           .add(EnumJsonAdapter.create(IsoCurrency.class)
               .withUnknownFallback(IsoCurrency.USD))
           .build();
    

    Note that this adapter is in the optional moshi-adapters module.

       implementation 'com.squareup.moshi:moshi-adapters:1.7.0'
    
    • New: Embed R8/ProGuard rules in the .jar file.
    • New: Use @CheckReturnValue in more places. We hope this will encourage you to use skipName() instead of nextName() for better performance!
    • New: Forbid automatic encoding of platform classes in androidx. As with java.*, android.*, and kotlin.* Moshi wants you to specify how to encode platform types.
    • New: Improve error reporting when creating an adapter fails.
    • New: Upgrade to Okio 1.15.0. We don't yet require Kotlin-friendly Okio 2.x but Moshi works fine with that release.
       implementation 'com.squareup.okio:okio:1.15.0'
    
    • Fix: Return false from JsonReader.hasNext() at document's end.
    • Fix: Improve code gen to handle several broken cases. Our generated adapters had problems with nulls, nested parameterized types, private transient properties, generic type aliases, fields with dollar signs in their names, and named companion objects.
  • v1.6.0 Changes

    May 15, 2018

    2018-05-14

    • Moshi now supports codegen for Kotlin. We've added a new annotation processor that generates a small and fast JSON adapter for your Kotlin types. It can be used on its own or with the existing KotlinJsonAdapterFactory adapter.

    • Moshi now resolves all type parameters. Previously Moshi wouldn't resolve type parameters on top-level classes.

    • New: Support up to 255 levels of nesting when reading and writing JSON. Previously Moshi would reject JSON input that contained more than 32 levels of nesting.

    • New: Write encoded JSON to a stream with JsonWriter.value(BufferedSource). Use this to emit a JSON value without decoding it first.

    • New: JsonAdapter.nonNull() returns a new JSON adapter that forbids explicit nulls in the JSON body. Use this to detect and fail eagerly on unwanted nulls.

    • New: JsonReader.skipName() is like nextName() but it avoids allocating when a name is unknown. Use this when JsonReader.selectName() returns -1.

    • New: Automatic module name of com.squareup.moshi for use with the Java Platform Module System. This moves moshi-adapters into its own .adapters package and forwards the existing adapter. It moves the moshi-kotlin into its own .kotlin.reflect package and forwards the existing adapter.

    • New: Upgrade to Okio 1.14.0.

       <dependency>
         <groupId>com.squareup.okio</groupId>
         <artifactId>okio</artifactId>
         <version>1.14.0</version>
       </dependency>
      
       com.squareup.okio:okio:1.14.0
      
    • Fix: Fail fast if there are trailing non-whitespace characters in the JSON passed to JsonAdapter.fromJson(String). Previously such data was ignored!

    • Fix: Fail fast when Kotlin types are abstract, inner, or object instances.

    • Fix: Fail fast if name() is called out of sequence.

    • Fix: Handle asymmetric Type.equals() methods when doing type comparisons. Previously it was possible that a registered type adapter would not be used because its Type.equals() method was not consistent with a user-provided type.

    • Fix: JsonValueReader.selectString() now returns -1 for non-strings instead of throwing.

    • Fix: Permit reading numbers as strings when the JsonReader was created from a JSON value. This was always supported when reading from a stream but broken when reading from a decoded value.

    • Fix: Delegate to user-adapters in the adapter for Object.class. Previously when Moshi encountered an opaque Object it would only use the built-in adapters. With this change user-installed adapters for types like String will always be honored.

  • v1.6.0-RC1

    May 07, 2018
  • v1.5.0 Changes

    May 15, 2017

    2017-05-14

    • Moshi now uses @Nullable to annotate all possibly-null values. We've added a compile-time dependency on the JSR 305 annotations. This is a [provided][maven_provided] dependency and does not need to be included in your build configuration, .jar file, or .apk. We use @ParametersAreNonnullByDefault and all parameters and return types are never null unless explicitly annotated @Nullable.

    • Warning: Moshi APIs in this update are source-incompatible for Kotlin callers. Nullability was previously ambiguous and lenient but now the compiler will enforce strict null checks.

    • Kotlin models are now supported via the moshi-kotlin extension. KotlinJsonAdapterFactory is the best way to use Kotlin with Moshi. It honors default values and is null-safe. Kotlin users that don't use this factory should write custom adapters for their JSON types. Otherwise Moshi cannot properly initialize delegated properties of the objects it decodes.

    • New: Upgrade to Okio 1.13.0.

       <dependency>
         <groupId>com.squareup.okio</groupId>
         <artifactId>okio</artifactId>
         <version>1.13.0</version>
       </dependency>
      
       com.squareup.okio:okio:1.13.0
      
    • New: You may now declare delegates in @ToJson and @FromJson methods. If one of the arguments to the method is a JsonAdapter of the same type, that will be the next eligible adapter for that type. This may be useful for composing adapters.

    • New: Types.equals(Type, Type) makes it easier to compare types in JsonAdapter.Factory.

    • Fix: Retain the sign on negative zero.

  • v1.4.0 Changes

    February 04, 2017

    2017-02-04

    Moshi 1.4 is a major release that adds JSON values as a core part of the library. We consider any Java object comprised of maps, lists, strings, numbers, booleans and nulls to be a JSON value. These 📜 are equivalent to parsed JSON objects in JavaScript, [Gson][gson]’s JsonElement, and [Jackson][jackson]’s JsonNode. Unlike Jackson and Gson, Moshi just uses Java’s built-in types for its values:

    JSON typeJava type {...}ObjectMap<String, Object> [...]ArrayList<Object> "abc"StringString 123NumberDouble, Long, or BigDecimal trueBooleanBoolean nullnullnull

    Moshi's new API JsonAdapter.toJsonValue() converts your application classes to JSON values comprised of the above types. Symmetrically, JsonAdapter.fromJsonValue() converts JSON values to your application classes.

    • New: JsonAdapter.toJsonValue() and fromJsonValue().
    • New: JsonReader.readJsonValue() reads a JSON value from a stream.
    • New: Moshi.adapter(Type, Class<? extends Annotation>) lets you look up the adapter for a qualified type.
    • New: JsonAdapter.serializeNulls() and indent() return JSON adapters that customize the format of the encoded JSON.
    • New: JsonReader.selectName() and selectString() optimize decoding JSON with known names and values.
    • New: Types.nextAnnotations() reduces the amount of code required to implement a custom JsonAdapter.Factory.
    • Fix: Don't fail on large longs that have a fractional component like 9223372036854775806.0.
  • v1.3.1 Changes

    October 21, 2016

    2016-10-21

    • Fix: Don't incorrectly report invalid input when a slash character is escaped. When we tightened our invalid escape handling we missed the one character that is valid both escaped \/ and unescaped /.
  • v1.3.0 Changes

    October 15, 2016

    2016-10-15

    • New: Permit @ToJson and @FromJson methods to take any number of JsonAdapter parameters to delegate to. This is supported for @ToJson methods that take a JsonWriter and @FromJson methods that take a JsonReader.
    • New: Throw JsonEncodingException when the incoming data is not valid JSON. Use this to differentiate data format problems from connectivity problems.
    • New: Upgrade to Okio 1.11.0.

      <dependency>
        <groupId>com.squareup.okio</groupId>
        <artifactId>okio</artifactId>
        <version>1.11.0</version>
      </dependency>
      
    • New: Omit Kotlin (kotlin.*) and Scala (scala.*) platform types when encoding objects using their fields. This should make it easier to avoid unexpected dependencies on platform versions.

    • Fix: Explicitly limit reading and writing to 31 levels of nested structure. Previously no specific limit was enforced, but deeply nested documents would fail with either an ArrayIndexOutOfBoundsException due to a bug in JsonWriter's path management, or a StackOverflowError due to excessive recursion.

    • Fix: Require enclosed types to specify their enclosing type with Types.newParameterizedTypeWithOwner(). Previously this API did not exist and looking up adapters for enclosed parameterized types was not possible.

    • Fix: Fail on invalid escapes. Previously any character could be escaped. With this fix only characters permitted to be escaped may be escaped. Use JsonReader.setLenient(true) to read JSON documents that escape characters that should not be escaped.

  • v1.2.0 Changes

    May 28, 2016

    2016-05-28

    • New: Take advantage of Okio's new Options feature when reading field names and enum values. This has a significant impact on performance. We measured parsing performance improve from 89k ops/sec to 140k ops/sec on one benchmark on one machine.
    • New: Upgrade to Okio 1.8.0.

      <dependency>
        <groupId>com.squareup.okio</groupId>
        <artifactId>okio</artifactId>
        <version>1.8.0</version>
      </dependency>
      
    • New: Support types that lack no-argument constructors objects on Android releases prior to Gingerbread.

    • Fix: Add writer value overload for boxed booleans. Autoboxing resolves boxed longs and doubles to value(Number), but a boxed boolean would otherwise resolve to value(boolean) with an implicit call to booleanValue() which has the potential to throw NPEs.

    • Fix: Be more aggressive about canonicalizing types.

  • v1.1.0 Changes

    January 18, 2016

    2016-01-19

    • New: Support [RFC 7159][rfc_7159], the latest JSON specification. This removes the constraint that the root value must be an array or an object. It may now take any value: array, object, string, number, boolean, or null. Previously this was only permitted if the adapter was configured to be lenient.
    • New: Enum constants may be annotated with @Json to customize their encoded value.
    • New: Create new builder from Moshi instance with Moshi.newBuilder().
    • New: Types.getRawType() and Types.collectionElementType() APIs to assist in defining generic type adapter factories.
  • v1.0.0 Changes

    2015-09-27

    • API Change: Replaced new JsonReader() with JsonReader.of() and new JsonWriter() with JsonWriter.of(). If your code calls either of these constructors it will need to be updated to call the static factory method instead.
    • API Change: Don’t throw IOException on JsonAdapter.toJson(T). Code that calls this method may need to be fixed to no longer catch an impossible IOException.
    • Fix: the JSON adapter for Object no longer fails when encountering null in the stream.
    • New: @Json annotation can customize a field's name. This is particularly handy for fields whose names are Java keywords, like default or public.
    • New: Rfc3339DateJsonAdapter converts between a java.util.Date and a string formatted with RFC 3339 (like 2015-09-26T18:23:50.250Z). This class is in the new moshi-adapters subproject. You will need to register this adapter if you want this date formatting behavior. See it in action in the [dates example][dates_example].
    • New: Moshi.adapter() keeps a cache of all created adapters. For best efficiency, application code should keep a reference to required adapters in a field.
    • New: The Types factory class makes it possible to compose types like List<Card> or Map<String, Integer>. This is useful to look up JSON adapters for parameterized types.
    • New: JsonAdapter.failOnUnknown() returns a new JSON adapter that throws if an unknown value is encountered on the stream. Use this in development and debug builds to detect typos in field names. This feature shouldn’t be used in production because it makes migrations very difficult.