Error Handling

Mon, 01 Jan 0001 00:00:00 +0000

Error Handling

If a container fails to boot, you need to know exactly where the wiring failed. Rays replaces standard Go error handling during the lifecycle with a richer Error interface that captures stack traces and key-value attributes automatically.

import . "github.com/BeamFoundry/rays/pkg/lang"

func (s *UserService) PostConstruct() Error {
 if s.db == nil {
 err := NewError("WiringError", "Database pointer is nil")

 // AddAttribute does not return the Error object, so it cannot be chained.
 err.AddAttribute("component", "UserService")
 err.AddAttribute("action", "PostConstruct")

 return err
 }
 return nil
}

Integration with Logging

Because Rays integrates its lang package directly with the logging framework (covered in Chapter 4), an Error can report itself seamlessly.

Enum Types

Mon, 01 Jan 0001 00:00:00 +0000

Type-Safe Enums

Go does not have native, strict enums. This often leads to configuration bugs where an invalid string from a YAML file is happily parsed into a string field, only to fail deep within the application logic.

Rays solves this with Enum[T]. It strictly binds string values from YAML into custom Go types and validates them during the framework’s Instantiation phase.

1. Define the Enum Type

You can define your enums using a struct to hold the variants as fields.

5. Language Helpers on BeamFoundry Rays Core

Error Handling

Error Handling

Integration with Logging

Enum Types

Type-Safe Enums

1. Define the Enum Type