Errors¶

easeo uses one error hierarchy across all three languages. In Python, every error also inherits from ValueError, so existing code that catches ValueError keeps working.

The hierarchy¶

EaseoError
├── InvalidUrlError
├── ConfigurationError
├── EntityError
├── SchemaError
└── ContractError

Catching¶

from easeo import ConfigurationError, EaseoError

try:
    SEOConfig(canonical_host="", public_base_url="https://example.com")
except ConfigurationError as err:
    print("bad config:", err)
except EaseoError as err:
    print("some other easeo error:", err)

# ValueError also catches every easeo error:
try:
    SEOConfig(canonical_host="", public_base_url="https://example.com")
except ValueError as err:
    print("caught as ValueError:", err)

const { buildSeoPayload, ConfigurationError, EaseoError } = require("@easeo/core");

try {
  buildSeoPayload({ entityType: "page" }, "/x", {
    canonicalHost: "",
    publicBaseUrl: "",
  });
} catch (err) {
  if (err instanceof ConfigurationError) {
    console.log("bad config:", err.code); // "EASEO_CONFIGURATION"
  } else if (err instanceof EaseoError) {
    console.log("other easeo error:", err.message);
  }
}

JavaScript error codes¶

Every error class carries a stable code:

Argument errors¶

In JavaScript, a missing or wrong-typed argument raises TypeError with a message naming the function and parameter:

normalizePath: expected 'path' to be a string, received type undefined

Python raises TypeError for the same class of mistake.

Recap¶

• One hierarchy, five concrete types, one base.
• Python errors are also ValueError.
• JavaScript errors carry a stable code.