Tag: Resolver
-
Post Views: 24 1. GraphQL architecture is defined as follows 2. Print the output 1 in the method __invoke in the class TemplateDetailsResolver, not output. as shown in Figure 1 3. The GraphQL schema definition is restored as follows, then the corresponding class method __invoke can be executed. as shown in Figure 2 4. Decide to split the GraphQL schema…
-
Post Views: 22 1. In Lighthouse 5, an error is reported: illuminate\contracts\container\bindingResolutionException : target[Interface]Is not instantiable while building[Resolver]… as shown in Figure 1 2. Edit ThemeStoreGraphQL/Resources/GraphQL/Theme_Setting.GraphQL , comment out: TemplateSettingsData(BaseName: String!):[ThemeSection]@field(resolver: “modules\\themestoreGraphQL\\resolver\\onlinestoreetheme\\TemplateSettingsDataResolver”). Then no errors will be reported. 3. After uncommenting, check ThemeStoreGraphQL/Resolver/OnlineStoreEtheme/TemplateSettingsDateResolver.php . TemplateSchemaLoaderInterface is passed as a parameter to the constructor. 4. Check the service provider class of…
-
Post Views: 20 1. Error in Laravel 6: Target[Interface]Is not instantiable while building[Resolver]. as shown in Figure 1 2. View git logs, analyze /modules/themestore/providers/themestoreServiceProvider.php, send Now there is a shared binding registered in the container: ThemeConfigLoaderInterface::Class, but now it does not exist. as shown in Figure 2 3. Finally found this shared binding: ThemeConfigLoaderInterface::Class has been moved to /modules/themesetting/providers/themesettingServiceProvider.php 4.…
-
Post Views: 17 1. The name of the table field is in the form of lowercase letters and underscores. as shown in Figure 1 2. The interface is implemented based on GraphQL, and the field name that is specified as the interface response must be in the form of hump. 3. Print the parser /modules/themestore/resolver/onlinestoreetheme/themeassesResolver.php method $themeAssets, the object property…