Exceptions

All of the package’s own exceptions extend TranslatableException, so you can catch the whole family with the base class. Only a misconfigured setting throws the toolkit’s InvalidConfigurationException instead:

use RoundlyConsulting\Translatable\Exceptions\InvalidLocaleException;
use RoundlyConsulting\Translatable\Exceptions\TranslatableException;

try {
    $topic->setTranslations('name', $payload);
} catch (InvalidLocaleException $e) {
    // malformed key, or an unsupported locale while strict_locales is on
} catch (TranslatableException $e) {
    // any other package error
}

To avoid write-path exceptions from user input altogether, normalise request maps with Translatable::fromInput() or validate them with Translatable::rules() first (see Input and validation). A single locale from a query parameter or route segment goes through Translatable::ensureLocale() or Translatable::isSupported().