Allow custom scope resolvers for things like userId, organizationId, creatorId, tenantId

[RichardLindhout]

We now have some check for userId, organizationId, userOrganizationId which are used at webRidge.

This won't work for other thing like authorId, or creatorId. User from a GraphQL api is generally not allowed to put this field inside of the api, this field needs to be resolved based on auth context or something else.

We need to support his use case by deprecating the userId, organizationId, userOrganizationId fields https://github.com/web-ridge/gqlgen-sqlboiler/blob/master/resolver.gotpl#L110.

Instead user would be allowed to put a resolver config object inside the convert_plugin.go

Instead of

api.AddPlugin(gbgen.NewResolverPlugin(
            convertHelpersDir,
            sqlboilerDir,
            gqlgenModelDir,
            "github.com/yourauth/implementation" // leave empty if you don't have auth
        )),

Maybe something like this

api.AddPlugin(gbgen.NewResolverPlugin(
            convertHelpersDir,
            sqlboilerDir,
            gqlgenModelDir,
            &gqlgen.ResolverConfig{
                []CustomImport{
                    {
                        Alias: "auth",
                        Package: "github.com/yourauth/implementation",
                    },
                },
                []ResolveIDs{
                    {
                        BoilerColumnName: "userID",
                        Resolver: "auth.UserIDFromContext",
                        NullResolver: "auth.NullableUserIDFromContext",
                    },
                }
        )),

[RichardLindhout]

@troian I think you have this use-case too right? Based on creatorId in your scheme

[troian]

Exactly!

[RichardLindhout]

Ok, I'll try to resolve this issue this week!

[RichardLindhout]

This is finished in #development will try to release this soon!

[RichardLindhout]

api.AddPlugin(gbgen.NewResolverPlugin(
            output,
            backend,
            frontend,
            gbgen.ResolverPluginConfig{
                // Authorization scopes can be used to override e.g. userId, organizationId, tenantId
                // This will be resolved used the provided ScopeResolverName if the result of the AddTrigger=true
                // You would need this if you don't want to require these fields in your schema but you want to add them
                // to the db model.
                // If you do have these fields in your schema but want them authorized you could use a gqlgen directive
                AuthorizationScopes: []*gbgen.AuthorizationScope{
                    {
                        ImportPath:        "github.com/.../app/backend/auth",
                        ImportAlias:       "auth",
                        ScopeResolverName: "UserIDFromContext", // function which is called with the context of the resolver
                        BoilerColumnName:  "UserID",

                        AddHook: func(model *gbgen.BoilerModel, resolver *gbgen.Resolver, templateKey string) bool {
                            fmt.Println(templateKey)
                            // templateKey contains a unique where the resolver tries to add something
                            // e.g.
                            // most of the time you can ignore this
                            var addResolver bool
                            for _, field := range model.Fields {
                                if field.Name == "UserID" {
                                    addResolver = true
                                }
                            }
                            return addResolver
                        },
                    },
                },
            },
        )),

[RichardLindhout]

Is released in v3.1.0