Download the PHP package oxid-esales/graphql-configuration-access without Composer

On this page you can find all versions of the php package oxid-esales/graphql-configuration-access. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package graphql-configuration-access

Development Latest Version PHP Version

Quality Gate Status Coverage Technical Debt

graphql-configuration-access

OXAPI (GraphQL based) access to configuration settings

Why we use this schema

To fetch and update the configurations we implemented a different query/mutation per value-type. We have chosen this schema because of GraphQL's strictness which doesn't allow for dynamic types. Without these types, the API consumer would always have to convert the value after queries or before mutations if, for example, we decided to use json encoded strings instead.

To get the specific type of a configuration, we provide queries like shopSettings/moduleSettings/themeSettings to figure out the type for configurations. As a result you get an array of setting types:

Documentation

Install

Switch to the shop root directory (the file composer.json and the directories source/ and vendor/ are located there).

If you didn't have the oxid-esales/graphql-base module installed, composer will do that for you.

After installing the module, you need to activate it, either via OXID eShop admin or CLI.

How to use

A good starting point is to check the How to use section in the GraphQL Base Module

Blocking modules from de/activation via GraphQL

The file module_blockilst.yaml contains a list of modules which are necessary to handle configurations or de/activate modules via GraphQL or should be blocked for de/activation via GraphQL in general. Modules like oe_graphql_base and oe_graphql_configuration_access are listed there.

Testing

Linting, syntax check, static analysis

Unit/Integration/Acceptance tests

All versions of graphql-configuration-access with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2
doctrine/dbal Version ^v2.7
oxid-esales/graphql-base Version ^v10.0.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package oxid-esales/graphql-configuration-access contains the following files

Loading the files please wait ....