-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Comparing changes
Open a pull request
base repository: 99designs/gqlgen
base: v0.17.75
head repository: 99designs/gqlgen
compare: v0.17.76
- 11 commits
- 65 files changed
- 6 contributors
Commits on Jun 16, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 3654b05 - Browse repository at this point
Copy the full SHA 3654b05View commit details
Commits on Jun 23, 2025
-
chore(deps): bump github.com/go-viper/mapstructure/v2 in /_examples (#…
…3747) Bumps [github.com/go-viper/mapstructure/v2](https://github.com/go-viper/mapstructure) from 2.2.1 to 2.3.0. - [Release notes](https://github.com/go-viper/mapstructure/releases) - [Changelog](https://github.com/go-viper/mapstructure/blob/main/CHANGELOG.md) - [Commits](go-viper/mapstructure@v2.2.1...v2.3.0) --- updated-dependencies: - dependency-name: github.com/go-viper/mapstructure/v2 dependency-version: 2.3.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 14c8366 - Browse repository at this point
Copy the full SHA 14c8366View commit details -
chore(deps-dev): bump vitest from 3.2.3 to 3.2.4 in /integration (#3745)
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.3 to 3.2.4. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.2.4/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 3.2.4 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for e95f3b4 - Browse repository at this point
Copy the full SHA e95f3b4View commit details -
chore(deps): bump github.com/go-viper/mapstructure/v2 (#3746)
Bumps [github.com/go-viper/mapstructure/v2](https://github.com/go-viper/mapstructure) from 2.2.1 to 2.3.0. - [Release notes](https://github.com/go-viper/mapstructure/releases) - [Changelog](https://github.com/go-viper/mapstructure/blob/main/CHANGELOG.md) - [Commits](go-viper/mapstructure@v2.2.1...v2.3.0) --- updated-dependencies: - dependency-name: github.com/go-viper/mapstructure/v2 dependency-version: 2.3.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for a31de27 - Browse repository at this point
Copy the full SHA a31de27View commit details
Commits on Jun 24, 2025
-
Improve gqlgen performance by bulking name only package loads (#3743)
* Bulk load name only packages * Add tests * fix linter & bug * Additional load improvement, CR
Configuration menu - View commit details
-
Copy full SHA for be74a5b - Browse repository at this point
Copy the full SHA be74a5bView commit details -
Fix/explicit requires with mutli entity resolver (#3744)
This is a PR addressing this issue: #3742 These changes ensure that `explicit_requires` is respected and used even when `@entityResolver(multi: true)`. Prior to this schema generation would fail if you required fields from an field of type [object]. Also the Populate functions for `explicit_requires` would not be respected when `@entityResolver(multi: true)`. Example of failed generation schema: ``` type Product @key(fields: "id") @entityResolver(multi: true) { id: ID! someField: [SomeItem!] price: Float! @requires(fields: "someField {key value}") @gofield(forceResolver: true) } type SomeItem { key: String! value: String! } ``` I have: - [x] Added tests covering the bug / feature (see [testing](https://github.com/99designs/gqlgen/blob/master/TESTING.md)) - [ ] Updated any relevant documentation (see [docs](https://github.com/99designs/gqlgen/tree/master/docs/content))
Configuration menu - View commit details
-
Copy full SHA for 74ff0f8 - Browse repository at this point
Copy the full SHA 74ff0f8View commit details
Commits on Jun 26, 2025
-
fix use_function_syntax_for_execution_context with @goEnum/@GoModel (#…
…3748) * fix use_function_syntax_for_execution_context with @goEnum/@GoModel Adds a fix for #3605 to allow using both the use_function_syntax_for_execution_context option with binding enums to types with `@goModel` and `@goEnum` by creating a unique type for marshal/unmarshal of these enums. * fix tests Had the wrong capitalization that was expected in tests.
Configuration menu - View commit details
-
Copy full SHA for af75691 - Browse repository at this point
Copy the full SHA af75691View commit details
Commits on Jun 27, 2025
-
Attempt to preserve types (#3749)
Signed-off-by: Steve Coffman <steve@khanacademy.org>
Configuration menu - View commit details
-
Copy full SHA for 01d4e04 - Browse repository at this point
Copy the full SHA 01d4e04View commit details
Commits on Jun 28, 2025
-
Update github.com/vektah/gqlparser/v2 to v2.5.30 (#3751)
* Update github.com/vektah/gqlparser/v2@v2.5.29 Signed-off-by: Steve Coffman <steve@khanacademy.org> * Adjust to pass linting Signed-off-by: Steve Coffman <steve@khanacademy.org> * Fix mistake pointed out by \@tomoikey Signed-off-by: Steve Coffman <steve@khanacademy.org> * Update to gqlparser v2.5.30 Signed-off-by: Steve Coffman <steve@khanacademy.org> --------- Signed-off-by: Steve Coffman <steve@khanacademy.org>
Configuration menu - View commit details
-
Copy full SHA for c2ce357 - Browse repository at this point
Copy the full SHA c2ce357View commit details -
chore(deps): bump the go_modules group across 3 directories with 1 up…
…date (#3750) Bumps the go_modules group with 1 update in the /_examples/large-project-structure/main directory: [github.com/go-viper/mapstructure/v2](https://github.com/go-viper/mapstructure). Bumps the go_modules group with 1 update in the /_examples/mini-habr-with-subscriptions directory: [github.com/go-viper/mapstructure/v2](https://github.com/go-viper/mapstructure). Bumps the go_modules group with 1 update in the /_examples/websocket-initfunc/server directory: [github.com/go-viper/mapstructure/v2](https://github.com/go-viper/mapstructure). Updates `github.com/go-viper/mapstructure/v2` from 2.2.1 to 2.3.0 - [Release notes](https://github.com/go-viper/mapstructure/releases) - [Changelog](https://github.com/go-viper/mapstructure/blob/main/CHANGELOG.md) - [Commits](go-viper/mapstructure@v2.2.1...v2.3.0) Updates `github.com/go-viper/mapstructure/v2` from 2.2.1 to 2.3.0 - [Release notes](https://github.com/go-viper/mapstructure/releases) - [Changelog](https://github.com/go-viper/mapstructure/blob/main/CHANGELOG.md) - [Commits](go-viper/mapstructure@v2.2.1...v2.3.0) Updates `github.com/go-viper/mapstructure/v2` from 2.2.1 to 2.3.0 - [Release notes](https://github.com/go-viper/mapstructure/releases) - [Changelog](https://github.com/go-viper/mapstructure/blob/main/CHANGELOG.md) - [Commits](go-viper/mapstructure@v2.2.1...v2.3.0) --- updated-dependencies: - dependency-name: github.com/go-viper/mapstructure/v2 dependency-version: 2.3.0 dependency-type: indirect dependency-group: go_modules - dependency-name: github.com/go-viper/mapstructure/v2 dependency-version: 2.3.0 dependency-type: indirect dependency-group: go_modules - dependency-name: github.com/go-viper/mapstructure/v2 dependency-version: 2.3.0 dependency-type: indirect dependency-group: go_modules ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 47c3de5 - Browse repository at this point
Copy the full SHA 47c3de5View commit details -
Configuration menu - View commit details
-
Copy full SHA for a1b9849 - Browse repository at this point
Copy the full SHA a1b9849View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.17.75...v0.17.76