Skip to content

Releases: drizzle-team/drizzle-graphql

0.8.5

12 Aug 16:41
c558249
Compare
Choose a tag to compare
  • Fixed fields not being selected properly from fragments

0.8.4

13 Jun 06:24
3173e12
Compare
Choose a tag to compare
  • Added library name to error message for easier debugging
  • Fixed lack of library's own error messages on empty\absent schema in drizzle instance

0.8.3

07 Jun 14:57
c0b794e
Compare
Choose a tag to compare
  • Fixed type mismatch in entities

0.8.2

01 Jun 17:10
24aa77f
Compare
Choose a tag to compare
  • Readme fix (no code changes)

0.8.1

28 May 22:47
338fb72
Compare
Choose a tag to compare
  • Added support for enums with incompatible with GraphQL naming limitation values

💬 : Now incompatible enum options will be named Opton${optionNumber}.
The actual value in such cases could be found in type description prefixed with Value: .

0.8.0

28 May 22:23
2986f94
Compare
Choose a tag to compare
  • Added config option to limit depth of relations

0.7.3

28 May 13:50
4055a35
Compare
Choose a tag to compare
  • Added input type caching for reduced memory usage

0.7.2

27 May 13:13
6c727d5
Compare
Choose a tag to compare
  • Fixed relation data selection on tables with typescript names with lowercase first letter

0.7.1

26 May 17:57
47fb8ab
Compare
Choose a tag to compare
  • Fixed relation selection ignore on aliased relations

0.7.0

25 May 21:27
4cc3c55
Compare
Choose a tag to compare
  • Added deep relations

❓ : How deep?
For each branch of table's relations, they are generated until the same table gets used twice. Upon second hit, table will still be generated, but will have no relations

❓ : Why are relations not recursive?
Recursive types are not supported by GraphQL

⚠️ : Resolver return Typescript types have not been updated yet, this will be added in a next patch.