Configuration

1. # Configuration
2. # Accessing Configuration Values
3. # Defining Configuration Values
4. # Extensions

#Configuration

All of the configuration files for the TypeRocket are stored in the config directory.

#Accessing Configuration Values

You can access the values stored in a config file using dot notation within the tr_config() function. For example, app.debug will locate the key debug inside the app.php file.

$value = tr_config('app.debug');

You can also set a default value if no value can be found.

$value = tr_config('app.debug', false);

#Defining Configuration Values

Because WordPress uses constants for user-defined variables over env variables, TypeRocket provides the immutable() function for accessing a constant but also provides a default value if it is not found.

immutable('WP_DEBUG', true);

You can use this function when creating your configuration options.

#Extensions

In your config/app.php file, you can add and remove extensions loaded by TypeRocket.

The extensions settings take a key-value array of with key as the class name and the value as an array of arguments that will be used by the extension class' constructor.

/*  
|--------------------------------------------------------------------------  
| Extensions  
|--------------------------------------------------------------------------  
|  
| The class names of the TypeRocket extensions you wish to enable.  
|  
*/  
'extensions' => [  
  '\TypeRocket\Extensions\Seo' => [ null ],  
  '\TypeRocket\Extensions\PageBuilder' => null,  
  '\TypeRocket\Extensions\PostTypesUI' => null,  
  '\TypeRocket\Extensions\ThemeOptions' => null,  
  '\TypeRocket\Extensions\DevTools' => [ true ],  
  '\TypeRocket\Extensions\PostMessages' => null,  
  '\TypeRocket\Extensions\Gutenberg' => [ true ],  
],