From 37f57a897eb271cdcf07a54e2504057dcdbdb772 Mon Sep 17 00:00:00 2001 From: Yogesh Valiya <66505755+yogesh-valiya@users.noreply.github.com> Date: Sat, 11 May 2024 13:34:27 +0530 Subject: [PATCH 1/2] Update required-configuration-files.md Added `graphql` --- src/pages/development/build/required-configuration-files.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/pages/development/build/required-configuration-files.md b/src/pages/development/build/required-configuration-files.md index ad69a2ae1..907b1d414 100644 --- a/src/pages/development/build/required-configuration-files.md +++ b/src/pages/development/build/required-configuration-files.md @@ -39,11 +39,12 @@ In addition to those files, a module also has nested configuration directories i * `/etc/frontend/` * `/etc/webapi_rest/` * `/etc/webapi_soap/` +* `/etc/graphql/` ### Global vs local * Configuration files that are in the top level of that module's `etc` directory are global to that component. -* Configuration files placed in subdirectories (`adminhtml`, `frontend`, `webapi_rest`, `webapi_soap`) apply only to those respective functional areas. +* Configuration files placed in subdirectories (`adminhtml`, `frontend`, `webapi_rest`, `webapi_soap`, `graphql`) apply only to those respective functional areas. ### Requirements @@ -57,9 +58,10 @@ Similarly, if your module changes the UI, you should add the needed configuratio * `/etc/frontend/di.xml` * `/etc/frontend/page_types.xml` -If the module is a service that may call an API, or does some other work that is not manifested in the UI you should add any needed configuration files in the REST and/or SOAP webapi configuration directories, like this: +If the module is a service that may call an API, or does some other work that is not manifested in the UI you should add any needed configuration files in the GraphQA, REST, and/or SOAP webapi configuration directories, like this: * `/etc/webapi_rest/di.xml` * `/etc/webapi_soap/di.xml` +* `/etc/graphql/di.xml` Keep in mind that you might be able to handle your module's configuration solely with configuration files at the top level of your module's `etc` directory, but the nested directory is a useful way to keep the configuration neatly compartmentalized. From 98db01124bf571fa2542a7f59f898f8232ceb8ae Mon Sep 17 00:00:00 2001 From: Yogesh Valiya <66505755+yogesh-valiya@users.noreply.github.com> Date: Sat, 11 May 2024 13:36:33 +0530 Subject: [PATCH 2/2] Update required-configuration-files.md --- src/pages/development/build/required-configuration-files.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/pages/development/build/required-configuration-files.md b/src/pages/development/build/required-configuration-files.md index 907b1d414..ef38bf6de 100644 --- a/src/pages/development/build/required-configuration-files.md +++ b/src/pages/development/build/required-configuration-files.md @@ -37,14 +37,14 @@ In addition to those files, a module also has nested configuration directories i * `/etc/adminhtml/` * `/etc/frontend/` +* `/etc/graphql/` * `/etc/webapi_rest/` * `/etc/webapi_soap/` -* `/etc/graphql/` ### Global vs local * Configuration files that are in the top level of that module's `etc` directory are global to that component. -* Configuration files placed in subdirectories (`adminhtml`, `frontend`, `webapi_rest`, `webapi_soap`, `graphql`) apply only to those respective functional areas. +* Configuration files placed in subdirectories (`adminhtml`, `frontend`, `graphql`, `webapi_rest`, `webapi_soap`) apply only to those respective functional areas. ### Requirements @@ -58,7 +58,7 @@ Similarly, if your module changes the UI, you should add the needed configuratio * `/etc/frontend/di.xml` * `/etc/frontend/page_types.xml` -If the module is a service that may call an API, or does some other work that is not manifested in the UI you should add any needed configuration files in the GraphQA, REST, and/or SOAP webapi configuration directories, like this: +If the module is a service that may call an API, or does some other work that is not manifested in the UI you should add any needed configuration files in the GraphQL, REST and/or SOAP webapi configuration directories, like this: * `/etc/webapi_rest/di.xml` * `/etc/webapi_soap/di.xml`