mirror of https://github.com/stashapp/stash.git synced 2026-01-19 14:42:00 +01:00

SmallCoccinelle 45f700d6ea

Support Go 1.18: Upgrade gqlgen to v0.17.2 (#2443 )

* Upgrade gqlgen to v0.17.2

This enables builds on Go 1.18. github.com/vektah/gqlparser is upgraded
to the newest version too.

Getting this to work is a bit of a hazzle. I had to first remove
vendoring from the repository, perform the upgrade and then re-introduce
the vendor directory. I think gqlgens analysis went wrong for some
reason on the upgrade. It would seem a clean-room installation fixed it.

* Bump project to 1.18

* Update all packages, address gqlgenc breaking changes

* Let `go mod tidy` handle the go.mod file

* Upgrade linter to 1.45.2

* Introduce v1.45.2 of the linter

The linter now correctly warns on `strings.Title` because it isn't
unicode-aware. Fix this by using the suggested fix from x/text/cases
to produce unicode-aware strings.

The mapping isn't entirely 1-1 as this new approach has a larger iface:
it spans all of unicode rather than just ASCII. It coincides for ASCII
however, so things should be largely the same.

* Ready ourselves for errchkjson and contextcheck.

* Revert dockerfile golang version changes for now

Co-authored-by: Kermie <kermie@isinthe.house>
Co-authored-by: WithoutPants <53250216+WithoutPants@users.noreply.github.com>

2022-04-02 18:08:14 +11:00

1.3 KiB

Raw Blame History

Contribution Guidelines

Want to contribute to gqlgen? Here are some guidelines for how we accept help.

Getting in Touch

Our discord server is the best place to ask questions or get advice on using gqlgen.

Reporting Bugs and Issues

We use GitHub Issues to track bugs, so please do a search before submitting to ensure your problem isn't already tracked.

New Issues

Please provide the expected and observed behaviours in your issue. A minimal GraphQL schema or configuration file should be provided where appropriate.

Proposing a Change

If you intend to implement a feature for gqlgen, or make a non-trivial change to the current implementation, we recommend first filing an issue marked with the proposal tag, so that the engineering team can provide guidance and feedback on the direction of an implementation. This also help ensure that other people aren't also working on the same thing.

Bug fixes are welcome and should come with appropriate test coverage.

New features should be made against the next branch.

License

By contributing to gqlgen, you agree that your contributions will be licensed under its MIT license.

1.3 KiB Raw Blame History