v0.7.0

🏠 Internal

• add slog to error reporting (#12) @gjarmstrong

📦 Dependencies

• Bump golang.org/x/net from 0.19.0 to 0.23.0 (#11) @dependabot

---

Contributors

@dependabot, @dependabot[bot], @gjarmstrong and @josemarluedke

---

For full changes, see the comparison between v0.6.0 and v0.7.0

v0.6.0

💥 Breaking Change

• chore: upgrade dependencies & update to go v1.21 (#10) @josemarluedke

---

Contributors

@josemarluedke and @strobus

---

For full changes, see the comparison between v0.5.2 and v0.6.0

v0.5.2

🐛 Bug Fix

• Try to unwrap go error instead of checking error messages (#8) @josemarluedke

---

Contributors

@josemarluedke

---

For full changes, see the comparison between v0.5.1 and v0.5.2

v0.5.1

🐛 Bug Fix

• Prevent replacing error when error is custom (#7) @josemarluedke

---

Contributors

@josemarluedke

---

For full changes, see the comparison between v0.5.0 and v0.5.1

v0.5.0

🚀 Enhancement

• Handle gqlgen fed entity error replacement (#6) @josemarluedke

---

Contributors

@josemarluedke

---

For full changes, see the comparison between v0.4.1 and v0.5.0

v0.4.1

🐛 Bug Fix

• Fix display error from runtime.TypeAssertionError (#3) @josemarluedke

---

Contributors

@josemarluedke

---

For full changes, see the comparison between v0.4.0 and v0.5.0

v0.4.0

• Drop support for go 1.12
• Refactor error handling for gqlgen v0.13 (removes the previous workaround from the last release)

---

Contributors

@josemarluedke

---

For full changes, see the comparison between v0.3.0 and v0.4.0

v0.3.0

• GraphQL wraps errors thrown in directives into a non-exported field. However, the Message field is copied to the outer error. This change allows encoded error information in the Message field to be used to generate a customError (github.com/nrfta/go-errors). The Message field should be formatted as <errorCode>;<message>.

---

Contributors

@strobus

---

For full changes, see the comparison between v0.2.0 and v0.3.0

v0.2.0

💥 Breaking Change

• Fix compat issues with latest gqlgen version (#2) @josemarluedke

📦 Dependencies

• Fix compat issues with latest gqlgen version (#2) @josemarluedke

---

Contributors

@josemarluedke

---

For full changes, see the comparison between v0.1.0 and v0.2.0

v0.1.0

🚀 Enhancement

• Initial Implementation (#1) @josemarluedke

---

Contributors

@josemarluedke