All Versions
116
Latest Version
Avg Release Cycle
-
Latest Release
-
Changelog History
Page 10
Changelog History
Page 10
-
v0.15.6 Changes
- ๐ Fix issue with incorrectly checking for generic types
-
v0.15.5 Changes
- ๐ Fix issue with array types in the dynamically generated type for lambdas
-
v0.15.4 Changes
- ๐ Fix issue where the generated GraphQL schema had the incorrect type for arrays (e.g. double[])
- ๐ Fix issue with
SchemaBuilder.FromObject
building invalid types from arrays.
-
v0.15.3 Changes
- ๐ Fix an issue where it would generate an invalid field name if we couldn't singularize the name
-
v0.15.2 Changes
- ๐ Move the query results into a
QueryResult
class so it is easier to work with
- ๐ Move the query results into a
-
v0.15.1 Changes
- ๐ Fix #11 - failure to use
RequiredField
with types likeuint
- it would try to initialise it with anint
- ๐ Fix #11 - failure to use
-
v0.15 Changes
- โ Remove old code that supported multiple fields with the same name and different arguments. GrpahQL doesn't support that and it caused a bug where it would sometimes not find the field you want. You can implment optional arguments and build a complex field like
schemaProvider.AddField("myField", new {name = (string)null, id = (Guid?)null}, (db, param) => param.id.HasValue ? db.MyEntities.Where(l => l.Id == param.id).FirstOrDefault() : db.MyEntities.Where(l => l.Name == param.name).FirstOrDefault(), "Returns an Entity object by ID or a match on the name argument");
- โ Remove old code that supported multiple fields with the same name and different arguments. GrpahQL doesn't support that and it caused a bug where it would sometimes not find the field you want. You can implment optional arguments and build a complex field like
-
v0.14.4 Changes
- ๐ Allow user to supply a type mapping for the generated GraphQL schema
-
v0.14.3 Changes
- ๐ Fix an issue where we would some time identify a type as IEnumerable when it shouldn't have been
- ๐ Allow
ReplaceField
on a sub type
-
v0.14.2 Changes
- Convert enums correctly