Custom config

Where to keep and how to access custom configuration key-value pairs? A fixed number of them that should be visible to all models and views. Is it a matter of just adding a new .php file to the config folder and returning an array? I need it to store some opcodes.

martinbean

1 month ago

Level 80

@developer654079525 Yes, you can create additional files in the config directory.

Personally, I put any configuration for third-party services (like API keys etc) in the existing config/services.php file. But for opcodes, I would define an enum rather than putting it in a configuration file:

namespace App\Enumerations;

enum Opcode: int
{
    case Good = 0;
    case Bad = 1;
}

You could then reference the values using Opcode::Good or Opcode::Bad.

Use enums to define possible values like this.

2 likes

Developer654079525

1 month ago

Level 2

What if the key-value pairs are string pairs? Wouldn't it then be much easier just to return an array of key-value pairs?

1 like

vincent15000

1 month ago

Level 63

In this case you can write a backed enum.

namespace App\Enumerations;

enum Opcode: string
{
    case Good = 'good';
    case Bad = 'bad';
}

https://www.php.net/manual/en/language.enumerations.backed.php

1 like

Please or to participate in this conversation.