> For the complete documentation index, see [llms.txt](https://xmlking.gitbook.io/yeti/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xmlking.gitbook.io/yeti/modules/libs/core.md).

# Core

This library was generated with [Nx](https://nx.dev).

This module should contain minimal shared `Guards`, `Services` , `State` Injectables

It should not contain `Components`, `Directives` and `Pipes`. For that, use `SharedModule`

> import **CoreModule** in only **AppModule**

### Service

1. AppConfigService - loading remote config and featureFlags
2. PageTitleService - set page title from breadcrumbs
3. AnalyticsService - Google Analytics

### Stores

1. AuthState - keep track of auth state

### Handlers

1. RouteHandler - update page title and send page views to google analytics

### Interceptors

1. ErrorInterceptor - report http errors

## Running unit tests

Run `nx test core` to execute the unit tests.

### Usage

> Eva Icons

```markup
<nb-icon
  icon="arrow-circle-right-outline"
  [options]="{ animation: { type: 'zoom' } }"
></nb-icon>
```

> Fontawesome icons

```markup
<nb-icon icon="star" pack="fas"></nb-icon>
<nb-icon icon="arrow-alt-circle-right" pack="far"></nb-icon>
```


---

# 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://xmlking.gitbook.io/yeti/modules/libs/core.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.
