Constants for statuses and data types with client-server architecture?

Question

Software design

public const TYPES
        = [
            self::TYPE_TV_SERIES,
            self::TYPE_FEATURE_FILM,
            self::TYPE_SHORT_FILM,
        ];
    public const TYPES_STR_CONST
        = [
            self::TYPE_TV_SERIES    => 'TYPE_TV_SERIES',
            self::TYPE_FEATURE_FILM => 'TYPE_FEATURE_FILM',
            self::TYPE_SHORT_FILM   => 'TYPE_SHORT_FILM',
        ];

Which approach would you choose and why?

Personally, I prefer to issue a constant string to the front and use the string, convert it to int and work with int, store int in the database. Let this add complexity in the form of "what and when to use", that is, lines only for working with the client side, but someone can use the constant for other purposes.

public function typeStrConst(): string {
        return EpisodeType::TYPES_STR_CONST[$this->type->value()];
    }
...

        <attribute name="typeStrConst" serialized-name="type">
            <group>non_sensitive_data</group>
            <group>public.info</group>
        </attribute>

Answer 1

In this particular case, these are not constants, but a separate reference book, which has no place in the code from the word at all