All Versions
116
Latest Version
Avg Release Cycle
-
Latest Release
-

Changelog History
Page 11

  • v0.14.1 Changes

    • 🛠 Fix SchemaGenerator to support arrays better
    • 👌 Support turning QueryRequest variables from JSON objects into their requied objects

  • v0.14.0 Changes

    • 👍 Bring back ReplaceField as technically GraphQL doesn't support overloading, so if you're using tools like Apollo etc to generate code you need to only have unique fields
    • ➕ Added GetGraphQLSchema on the schema to return a .graphql schema file for input into tools like Apollo codegen
    • ➕ Add the option to add descriptions to Mutations

  • v0.13.1 Changes

    • 🛠 Fix issue where operation name with no arguments failed

  • v0.13.0 Changes

    • 💥 Breaking change: Strings are now defined by double quotes " to fit in with GraphQL better
    • ➕ Added support to use a LINQ-style language as a argument in GraphQL. E.g the following GQL field, { users(filter: "active = true and age > 20") { id name } } can be defined with schema.AddField("users", new {filter = EntityQuery<User>()}, (ctx, p) => ctx.Users.Where(p.filter), "Return filtered users"). Letting you write that filter using any fields defined on the User object
    • ➕ Add null/empty constant for checking for null in EQL

  • v0.12.1 Changes

    • 🛠 Fix bug converting Int values to double? values

  • v0.12.0 Changes

    • 👌 Support field "overloads" - fields with same name and different arguments.

  • v0.11.0 Changes

    • 📦 Renamed package EntityGraphQL to emphasizes that it implements GraphQL

  • v0.10.1 Changes

    • 🛠 Fix issue with arrays and objects in variables parameter on the request
    • 👍 Better error messages when GraphQL arguments can't be mapped to an object
    • Validate required variables in operations are supplied in the variables dictionary
    • 🛠 Fix potential issue with selecting sub object graphs

  • v0.10.0 Changes

    • 🔄 Change the errors to appear in errors key along side data key as per GraphQL
    • 🛠 Fix an issue when selecting fields from a mutation result

  • v0.9.4 Changes

    • 👌 Support selecting an object that may be null { person {name} } person will be null if it does not exist