> For the complete documentation index, see [llms.txt](https://labrynx.gitbook.io/error-enhanced/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://labrynx.gitbook.io/error-enhanced/enums/severity.md).

# Severity

The `Severity` enum, part of the `error-enhanced` library, is designed to offer a standardized approach to categorizing the impact level of errors within a system. By doing so, it facilitates more effective error handling and debugging.

## Features

### Error Impact Classification

* Allows for sorting errors based on their impact level on system operations, enabling a more focused approach to troubleshooting.

### Versatility

* Since it's an enum, it's straightforward to extend or adapt to specific project needs, making it both reusable and maintainable.

### Type-Safety

* Written in TypeScript, it provides type-checking advantages, ensuring that the impact level is one of the predefined categories.

## Example Usage

```typescript
const sev = Severity.HIGH;
if (sev === Severity.CRITICAL) {
  // Trigger emergency alert
} else if (sev === Severity.HIGH) {
  // Log and notify admin
} else {
  // Handle less severe cases
}
```

## Extending and Customization

Since the enum is written in TypeScript, extending it or customizing it for specific use-cases is straightforward. For example, you could add a `NONE` member to indicate the absence of an error.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://labrynx.gitbook.io/error-enhanced/enums/severity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.