@anglr/datetime 9.0.2 → 9.0.3-beta.20260518114213

package/.claude/skills/angular-developer/references/signals-overview.md

@@ -0,0 +1,94 @@
+# Angular Signals Overview
+
+Signals are the foundation of reactivity in modern Angular applications. A **signal** is a wrapper around a value that notifies interested consumers when that value changes.
+
+## Writable Signals (`signal`)
+
+Use `signal()` to create state that can be directly updated.
+
+```ts
+import {signal} from '@angular/core';
+
+// Create a writable signal
+const count = signal(0);
+
+// Read the value (always requires calling the getter function)
+console.log(count());
+
+// Update the value directly
+count.set(3);
+
+// Update based on the previous value
+count.update((value) => value + 1);
+```
+
+### Exposing as Readonly
+
+When exposing state from a service, it is a best practice to expose a readonly version to prevent external mutation.
+
+```ts
+private readonly _count = signal(0);
+// Consumers can read this, but cannot call .set() or .update()
+readonly count = this._count.asReadonly();
+```
+
+## Computed Signals (`computed`)
+
+Use `computed()` to create read-only signals that derive their value from other signals.
+
+- **Lazily Evaluated**: The derivation function doesn't run until the computed signal is read.
+- **Memoized**: The result is cached. It only recalculates when one of the signals it depends on changes.
+- **Dynamic Dependencies**: Only the signals _actually read_ during the derivation are tracked.
+
+```ts
+import {signal, computed} from '@angular/core';
+
+const count = signal(0);
+const doubleCount = computed(() => count() * 2);
+
+// doubleCount automatically updates when count changes.
+```
+
+## Reactive Contexts
+
+A **reactive context** is a runtime state where Angular monitors signal reads to establish a dependency.
+
+Angular automatically enters a reactive context when evaluating:
+
+- `computed` signals
+- `effect` callbacks
+- `linkedSignal` computations
+- Component templates
+
+### Untracked Reads (`untracked`)
+
+If you need to read a signal inside a reactive context _without_ creating a dependency (so that the context doesn't re-run when the signal changes), use `untracked()`.
+
+```ts
+import {effect, untracked} from '@angular/core';
+
+effect(() => {
+  // This effect only runs when currentUser changes.
+  // It does NOT run when counter changes, even though counter is read here.
+  console.log(`User: ${currentUser()}, Count: ${untracked(counter)}`);
+});
+```
+
+### Async Operations in Reactive Contexts
+
+The reactive context is only active for **synchronous** code. Signal reads after an `await` will not be tracked. **Always read signals before asynchronous boundaries.**
+
+```ts
+// ❌ INCORRECT: theme() is not tracked because it is read after await
+effect(async () => {
+  const data = await fetchUserData();
+  console.log(theme());
+});
+
+// ✅ CORRECT: Read the signal before the await
+effect(async () => {
+  const currentTheme = theme();
+  const data = await fetchUserData();
+  console.log(currentTheme);
+});
+```

package/.claude/skills/angular-developer/references/tailwind-css.md

@@ -0,0 +1,69 @@
+# Using Tailwind CSS with Angular
+
+Tailwind CSS is a utility-first CSS framework that integrates seamlessly with Angular.
+
+**CRITICAL AGENT GUIDANCE: ALWAYS focus on Tailwind CSS v4 practices. DO NOT revert to old Tailwind v3 patterns (like creating `tailwind.config.js` with `@tailwind` directives) as this will break the application build. Modern Angular projects use Tailwind v4.**
+
+## Automated Setup (Recommended)
+
+The easiest way to add Tailwind CSS to an Angular project is via the Angular CLI:
+
+```shell
+ng add tailwindcss
+```
+
+This will automatically:
+
+1. Install `tailwindcss` and peer dependencies.
+2. Configure the project to use Tailwind CSS.
+3. Add the proper import to your global styles.
+
+## Manual Setup (Tailwind v4)
+
+If setting up manually, use the following Tailwind v4 pattern:
+
+### 1. Install Dependencies
+
+Install Tailwind CSS and PostCSS:
+
+```shell
+npm install tailwindcss @tailwindcss/postcss postcss
+```
+
+### 2. Configure PostCSS
+
+Create a `.postcssrc.json` file in the project root:
+
+```json
+{
+  "plugins": {
+    "@tailwindcss/postcss": {}
+  }
+}
+```
+
+_(Do NOT create a `tailwind.config.js` file! Configuration in v4 is handled through CSS variables)._
+
+### 3. Import Tailwind CSS
+
+In your global styles file (e.g., `src/styles.css`), add the standard v4 import:
+
+```css
+@import 'tailwindcss';
+```
+
+_(If using SCSS, use `@use 'tailwindcss';` instead)._
+
+### 4. Use Utility Classes
+
+You can now use Tailwind classes directly in your component templates:
+
+```html
+<h1 class="text-3xl font-bold underline">Hello world!</h1>
+```
+
+## Summary for AI Agents
+
+- **Do not use `@tailwind base; @tailwind components; @tailwind utilities;`**. Use `@import 'tailwindcss';`.
+- **Do not create `tailwind.config.js`**. Configuration is managed directly in CSS via theme variables or using PostCSS configurations.
+- Stick strictly to v4 syntax and workflows.

package/.claude/skills/angular-developer/references/template-driven-forms.md

@@ -0,0 +1,114 @@
+# Template-Driven Forms
+
+Template-driven forms use two-way data binding (`[(ngModel)]`) to update the data model in the component as changes are made in the template and vice versa. They are ideal for simple forms and use directives in the HTML template to manage form state and validation.
+
+## Core Directives
+
+Template-driven forms rely on the `FormsModule` which provides these key directives:
+
+- `NgModel`: Reconciles value changes in the form element with the data model (`[(ngModel)]`).
+- `NgForm`: Automatically creates a top-level `FormGroup` bound to the `<form>` tag.
+- `NgModelGroup`: Creates a nested `FormGroup` bound to a DOM element.
+
+## Setup
+
+First, import `FormsModule` into your component or module.
+
+```ts
+import {Component} from '@angular/core';
+import {FormsModule} from '@angular/forms';
+
+@Component({
+  selector: 'app-user-form',
+  imports: [FormsModule],
+  templateUrl: './user-form.component.html',
+})
+export class UserForm {
+  user = {name: '', role: 'Guest'};
+
+  onSubmit() {
+    console.log('Form submitted!', this.user);
+  }
+}
+```
+
+## Building the Form Template
+
+### Two-Way Binding with `[(ngModel)]`
+
+Use `[(ngModel)]` on input elements. **Every element using `[(ngModel)]` MUST have a `name` attribute.** Angular uses the `name` attribute to register the control with the parent `NgForm`.
+
+```html
+<form #userForm="ngForm" (ngSubmit)="onSubmit()">
+  <!-- Basic Input -->
+  <div>
+    <label for="name">Name:</label>
+    <input type="text" id="name" required [(ngModel)]="user.name" name="name" #nameCtrl="ngModel" />
+  </div>
+
+  <!-- Select Box -->
+  <div>
+    <label for="role">Role:</label>
+    <select id="role" [(ngModel)]="user.role" name="role">
+      <option value="Admin">Admin</option>
+      <option value="Guest">Guest</option>
+    </select>
+  </div>
+
+  <!-- Submit Button (disabled if form is invalid) -->
+  <button type="submit" [disabled]="!userForm.form.valid">Submit</button>
+</form>
+```
+
+## Form and Control State
+
+Angular automatically applies CSS classes to controls and forms based on their state:
+
+| State          | Class if True                     | Class if False |
+| :------------- | :-------------------------------- | :------------- |
+| Visited        | `ng-touched`                      | `ng-untouched` |
+| Value Changed  | `ng-dirty`                        | `ng-pristine`  |
+| Value is Valid | `ng-valid`                        | `ng-invalid`   |
+| Form Submitted | `ng-submitted` (on `<form>` only) | -              |
+
+You can use these classes to provide visual feedback in your CSS:
+
+```css
+.ng-valid[required],
+.ng-valid.required {
+  border-left: 5px solid #42a948; /* green */
+}
+.ng-invalid:not(form) {
+  border-left: 5px solid #a94442; /* red */
+}
+```
+
+## Validation and Error Messages
+
+To display error messages conditionally, export the `ngModel` directive to a template reference variable (e.g., `#nameCtrl="ngModel"`).
+
+```html
+<input type="text" id="name" required [(ngModel)]="user.name" name="name" #nameCtrl="ngModel" />
+
+<!-- Show error only if the control is invalid AND (touched OR dirty) -->
+@if (nameCtrl.invalid && (nameCtrl.dirty || nameCtrl.touched)) {
+<div class="alert alert-danger">
+  @if (nameCtrl.errors?.['required']) {
+  <div>Name is required.</div>
+  }
+</div>
+}
+```
+
+## Submitting the Form
+
+1. Use the `(ngSubmit)` event on the `<form>` element.
+2. Bind the submit button's disabled state to the overall form validity using the `NgForm` template reference variable (e.g., `[disabled]="!userForm.form.valid"`).
+
+## Resetting the Form
+
+To programmatically reset the form to its pristine state (clearing values and validation flags), use the `reset()` method on the `NgForm` instance.
+
+```html
+<button type="button" (click)="userForm.reset()">Reset</button>
+```

package/.claude/skills/angular-developer/references/testing-fundamentals.md

@@ -0,0 +1,66 @@
+# Testing Fundamentals
+
+This guide covers the fundamental principles and practices for writing unit tests in this repository, which uses Vitest as the test runner.
+
+## Core Philosophy: Zoneless & Async-First
+
+This project follows a modern, zoneless testing approach. State changes schedule updates asynchronously, and tests must account for this.
+
+**Do NOT** use `fixture.detectChanges()` to manually trigger updates.
+**ALWAYS** use the "Act, Wait, Assert" pattern:
+
+1.  **Act:** Update state or perform an action (e.g., set a component input, click a button).
+2.  **Wait:** Use `await fixture.whenStable()` to allow the framework to process the scheduled update and render the changes.
+3.  **Assert:** Verify the outcome.
+
+### Basic Test Structure Example
+
+```ts
+import {ComponentFixture, TestBed} from '@angular/core/testing';
+import {MyComponent} from './my.component';
+
+describe('MyComponent', () => {
+  let component: MyComponent;
+  let fixture: ComponentFixture<MyComponent>;
+  let h1: HTMLElement;
+
+  beforeEach(async () => {
+    // 1. Configure the test module
+    await TestBed.configureTestingModule({
+      imports: [MyComponent],
+    }).compileComponents();
+
+    // 2. Create the component fixture
+    fixture = TestBed.createComponent(MyComponent);
+    component = fixture.componentInstance;
+    h1 = fixture.nativeElement.querySelector('h1');
+  });
+
+  it('should display the default title', async () => {
+    // ACT: (Implicit) Component is created with default state.
+    // WAIT for initial data binding.
+    await fixture.whenStable();
+    // ASSERT the initial state.
+    expect(h1.textContent).toContain('Default Title');
+  });
+
+  it('should display a different title after a change', async () => {
+    // ACT: Change the component's title property.
+    component.title.set('New Test Title');
+
+    // WAIT for the asynchronous update to complete.
+    await fixture.whenStable();
+
+    // ASSERT the DOM has been updated.
+    expect(h1.textContent).toContain('New Test Title');
+  });
+});
+```
+
+## TestBed and ComponentFixture
+
+- **`TestBed`**: The primary utility for creating a test-specific Angular module. Use `TestBed.configureTestingModule({...})` in your `beforeEach` to declare components, provide services, and set up imports needed for your test.
+- **`ComponentFixture`**: A handle on the created component instance and its environment.
+  - `fixture.componentInstance`: Access the component's class instance.
+  - `fixture.nativeElement`: Access the component's root DOM element.
+  - `fixture.debugElement`: An Angular-specific wrapper around the `nativeElement` that provides safer, platform-agnostic ways to query the DOM (e.g., `debugElement.query(By.css('p'))`).

package/.github/instructions/typescript/code-conventions.md

@@ -0,0 +1,8 @@
+# Code conventions
+
+- Use Angular Developer skills and best practices whenever possible, but also:
+  - Always use explicit type annotations for class members even if type can be inferred even if it is not recommended by any skill
+  - Use `const` whenever possible, and only use `let` when variable needs to be reassigned
+  - For local constants, let typescript infer type if it is possible to infer it from initializer, otherwise use explicit type annotation
+  - Use `readonly` modifier for class members that are not reassigned after initialization
+  - Always use access modifiers for class members (private, protected, public)

package/.github/instructions/typescript/comments.md

@@ -0,0 +1,41 @@
+# Comments
+
+- Use JSDoc comments everywhere (classes, interfaces, types, functions, constants, properties, methods, parameters, etc.)
+- Use JSDoc for all members, also for private, protected
+- Use title `//######################### <name-of-title> #########################` for group of members in class or interface, where `<name-of-title>` is descriptive name of the group:
+  - supported names of titles are: `private fields`, `protected fields`, `protected properties`, `protected properties - template bindings`, `protected properties - children`, `public properties`, `public properties - inputs`, `public properties - outputs`, `public properties - models`, `constructor`, `public methods - implementation of <interface-name>`, `public methods`, `protected methods - template bindings`, `protected methods - overrides`, `protected methods`, `private methods`
+  - use empty line before and after title (except if its first line of the block)
+  - order members in class or interface according to the following rules (unless dependencies between members require different order):
+    - private fields
+    - protected fields
+    - protected properties
+    - protected properties - template bindings 
+    - protected properties - children
+    - public properties
+    - public properties - inputs
+    - public properties - outputs
+    - public properties - models
+    - constructor
+    - public methods - implementation of <interface-name>
+    - public methods
+    - protected methods - template bindings
+    - protected methods - overrides
+    - protected methods
+    - private methods
+  - when to use each group
+    - private fields - use this for all private properties
+    - protected fields - use this for all protected properties that are used only in component
+    - protected properties - use this only for getter and setter properties
+    - protected properties - template bindings  - use this for properties that are used in template
+    - protected properties - children - use this for Angular *view child/children* and *content child/children* properties
+    - public properties - use this for rest of public properties
+    - public properties - inputs - use this for Angular *inputs* properties
+    - public properties - outputs - use this for Angular *outputs* properties
+    - public properties - models - use this for Angular *model* properties
+    - constructor - use this only for constructor
+    - public methods - implementation of <interface-name> - use this for each method that was implemented by <interface-name>
+    - public methods - use this for rest of public methods
+    - protected methods - template bindings - use this for protected methdos that are used in template
+    - protected methods - overrides - use this for all protected methods that are overriden
+    - protected methods - use this for all protected methods that are used only in component
+    - private methods - use this for all private methods

package/.github/instructions/typescript/formatting.md

@@ -0,0 +1,43 @@
+# Formatting
+
+- Order typescript imports, use following rules:
+  - put `@angular/core` on first place
+  - then put other `@angular/core/*` imports
+  - then put other `@angular/*` imports
+  - then put `@anglr/*` imports
+  - then put `@jscrpt/common` and `@jscrpt/common/*` imports
+  - then put other *scoped* imports (e.g. `@fortawesome/*`, `@ngx-translate/*`, etc.)
+  - then other absolute imports
+  - then relative imports
+  - use empty line to separate absolute and relative imports
+- Use 4 spaces for indentation
+- For new lines use LF (line feed) character, not CRLF (carriage return + line feed)
+- Put empty line at the end of file
+- Always put opening braces on the new line, except case when object or array literal used together with `return` statement, in that case put opening brace on same line as `return`
+- Always use single quotes for strings
+- Always use semicolons at the end of statements
+- Always use block braces for control flow statements (if, for, while, switch), even if they are optional
+- Do not use braces around single parameter lambda functions, unless the parameter type is unknown
+- Do not use space after control flow statements (if, for, while, switch)
+- Do not put space after opening braces and before closing braces in oneline object literals, arrays, and function parameters, deconstructions, and imports (e.g. `import {Component} from '@angular/core';`, not `import { Component } from '@angular/core';`)
+- never wrap `import` statements, always keep them on one line, does not matter what is length of that line
+- Use empty line after before and after control flow statements (if, for, while, switch) (unless its first or last line of the block)
+- Always put comma after last item in array literal, after last property in object literal or after last argument in function definition when defined across multiple lines
+- Formatting arguments of function definition and declaration:
+  - Constructor arguments, put second and following arguments on new line, and align them with the first argument
+  - For other functions, if the function has more than 2 arguments and line length exceeds 120 characters, put second and following arguments on new line, and align them with the first argument
+- For method and function (also decorator use) calls:
+  - If there is only one parameter and it is not an object literal, keep it on the same line
+  - If there is only one parameter and it is lambda function, put body of lambda function on new line and use same indentation as previous line
+  - If there is only one paremeter and it is an object or array literal, put it on new line and use same indentation as previous line
+  - If there are more than one parameters and lenght does not exceed 120 characters, keep them on the same line
+  - If there are more than one parameters and lenght exceeds 120 characters, put second and following parameters on new line, and align them with the first parameter
+- Json literals:
+  - Put each property on new line and align them with the first property
+  - Opening and closing braces should be on their own line and aligned with the first property
+- Angular Component and Directive decorators:
+  - Follow rules for Json literals, but also:
+    - order properties in the following order: selector, templateUrl, template, styleUrl, styleUrls, styles, host, imports, providers, hostDirectives, changeDetection
+    - order array properties values in the following order: from shortest to longest (e.g. in `imports` property, put items with shorter names first)
+    - never use one line array or object literal for `imports`, `providers`, `host`
+    - always use `changeDetection: ChangeDetectionStrategy.OnPush`

package/.github/instructions/typescript/naming-conventions.md

@@ -0,0 +1,7 @@
+# Naming Conventions
+
+- Use PascalCase for component names, directives, pipes, services, interfaces, and type aliases
+- Use camelCase for variables, functions, and methods
+- Prefix private class members with underscore (_)
+- Do NOT prefix protected class members with underscore (_)
+- Use ALL_CAPS for constants

package/.github/instructions/typescript.instructions.md

@@ -0,0 +1,26 @@
+---
+description: This file describes the TypeScript code style, formatting, and conventions for the project.
+applyTo: "**/*.ts, **/*.js"
+---
+# Project general coding standards
+
+## Formatting
+
+For formatting instructions see [formatting instructions](./typescript/formatting.md).
+
+## Code conventions
+
+For code conventions instructions see [code conventions instructions](./typescript/code-conventions.md).
+
+## Comments
+
+For comments instructions see [comments instructions](./typescript/comments.md).
+
+## Naming Conventions
+
+For naming conventions instructions see [naming conventions instructions](./typescript/naming-conventions.md).
+
+## Error Handling
+
+- Use try/catch blocks for async operations
+- Always log errors with contextual information

package/changelog.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## Version 9.0.3 (2026-05-18)
+
+### Bug Fixes
+
+- fixed missing readme file
+
 ## Version 9.0.2 (2026-01-20)
 
 ### Bug Fixes

package/es2022/src/services/dateValueProvider/dateValueProvider.service.js

@@ -52,7 +52,7 @@ export class DateValueProvider {
         }
         return {
             from: start,
-            to: end
+            to: end,
         };
     }
     static { this.ɵfac = i0.ɵɵngDeclareFactory({ minVersion: "12.0.0", version: "19.1.0", ngImport: i0, type: DateValueProvider, deps: [{ token: DATE_API }], target: i0.ɵɵFactoryTarget.Injectable }); }

package/es2022/src/services/dateValueProvider/dateValueProvider.service.js.map

@@ -1 +1 @@
-{"version":3,"file":"dateValueProvider.service.js","sourceRoot":"","sources":["../../../../src/services/dateValueProvider/dateValueProvider.service.ts"],"names":[],"mappings":"AAAA,OAAO,EAAC,MAAM,EAAE,UAAU,EAAC,MAAM,eAAe,CAAC;AAGjD,OAAO,EAAC,QAAQ,EAAC,MAAM,mBAAmB,CAAC;;AAG3C;;GAEG;AAEH,MAAM,OAAO,iBAAiB;IAE1B,iEAAiE;IACjE,YAAwC,QAAwB;QAAxB,aAAQ,GAAR,QAAQ,CAAgB;IAEhE,CAAC;IAED,oEAAoE;IAEpE;;;;OAIG;IACI,QAAQ,CAAC,KAAY,EAAE,MAAc;QAExC,MAAM,GAAG,GAAG,IAAI,CAAC,QAAQ,CAAC,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC,CAAC;QAClD,MAAM,UAAU,GAAG,IAAI,CAAC,QAAQ,CAAC,SAAS,CAAC,MAAM,CAAC,CAAC;QACnD,IAAI,KAAK,GAAU,KAAK,CAAC;QACzB,IAAI,GAAG,GAAU,KAAK,CAAC;QAEvB,QAAQ;QACR,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EAC/B,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,aAAa,EAAE,CAAC,KAAK,CAAC;YAClC,GAAG,GAAG,GAAG,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC;QAClC,CAAC;QACD,MAAM;aACD,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EACpE,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC;YAChC,GAAG,GAAG,GAAG,CAAC,SAAS,EAAE,CAAC,KAAK,CAAC;QAChC,CAAC;QACD,KAAK;aACA,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EACpC,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,UAAU,EAAE,CAAC,KAAK,CAAC;YAC/B,GAAG,GAAG,GAAG,CAAC,QAAQ,EAAE,CAAC,KAAK,CAAC;QAC/B,CAAC;QACD,MAAM;aACD,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EACpC,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC;YAChC,GAAG,GAAG,GAAG,CAAC,SAAS,EAAE,CAAC,KAAK,CAAC;QAChC,CAAC;QACD,OAAO;aACF,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EACpC,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,YAAY,EAAE,CAAC,KAAK,CAAC;YACjC,GAAG,GAAG,GAAG,CAAC,UAAU,EAAE,CAAC,KAAK,CAAC;QACjC,CAAC;QACD,MAAM;aACD,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EACpE,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC;YAChC,GAAG,GAAG,GAAG,CAAC,SAAS,EAAE,CAAC,KAAK,CAAC;QAChC,CAAC;QAED,OAAO;YACH,IAAI,EAAE,KAAK;YACX,EAAE,EAAE,GAAG;SACV,CAAC;IACN,CAAC;8GA9DQ,iBAAiB,kBAGN,QAAQ;kHAHnB,iBAAiB,cADL,MAAM;;2FAClB,iBAAiB;kBAD7B,UAAU;mBAAC,EAAC,UAAU,EAAE,MAAM,EAAC;;0BAIf,MAAM;2BAAC,QAAQ","sourcesContent":["import {Inject, Injectable} from '@angular/core';\n\nimport {DateTimeValue} from '../../interfaces/dateTime/datetime.interface';\nimport {DATE_API} from '../../misc/tokens';\nimport {DateApi} from '../dateApi/dateApi.interface';\n\n/**\n * Class used for obtaining DateTimeValue for various formats\n */\n@Injectable({providedIn: 'root'})\nexport class DateValueProvider<TDate = unknown>\n{\n    //######################### constructor #########################\n    constructor(@Inject(DATE_API) protected _dateApi: DateApi<TDate>)\n    {\n    }\n\n    //######################### public methods #########################\n\n    /**\n     * Gets DateTimeValue from single value based on format\n     * @param value - Current value to be converted to ranged value\n     * @param format - Format that is requested to be displayed, it tells what range should be created\n     */\n    public getValue(value: TDate, format: string): DateTimeValue<TDate>\n    {\n        const val = this._dateApi.getValue(value, format);\n        const fullFormat = this._dateApi.getFormat(format);\n        let start: TDate = value;\n        let end: TDate = value;\n\n        //minute\n        if(fullFormat.indexOf('m') >= 0)\n        {\n            start = val.startOfMinute().value;\n            end = val.endOfMinute().value;\n        }\n        //hour\n        else if(fullFormat.indexOf('H') >= 0 || fullFormat.indexOf('h') >= 0)\n        {\n            start = val.startOfHour().value;\n            end = val.endOfHour().value;\n        }\n        //day\n        else if(fullFormat.indexOf('d') >= 0)\n        {\n            start = val.startOfDay().value;\n            end = val.endOfDay().value;\n        }\n        //week\n        else if(fullFormat.indexOf('w') >= 0)\n        {\n            start = val.startOfWeek().value;\n            end = val.endOfWeek().value;\n        }\n        //month\n        else if(fullFormat.indexOf('M') >= 0)\n        {\n            start = val.startOfMonth().value;\n            end = val.endOfMonth().value;\n        }\n        //year\n        else if(fullFormat.indexOf('Y') >= 0 || fullFormat.indexOf('y') >= 0)\n        {\n            start = val.startOfYear().value;\n            end = val.endOfYear().value;\n        }\n\n        return {\n            from: start,\n            to: end\n        };\n    }\n}"]}
+{"version":3,"file":"dateValueProvider.service.js","sourceRoot":"","sources":["../../../../src/services/dateValueProvider/dateValueProvider.service.ts"],"names":[],"mappings":"AAAA,OAAO,EAAC,MAAM,EAAE,UAAU,EAAC,MAAM,eAAe,CAAC;AAGjD,OAAO,EAAC,QAAQ,EAAC,MAAM,mBAAmB,CAAC;;AAG3C;;GAEG;AAEH,MAAM,OAAO,iBAAiB;IAE1B,iEAAiE;IACjE,YAAwC,QAAwB;QAAxB,aAAQ,GAAR,QAAQ,CAAgB;IAEhE,CAAC;IAED,oEAAoE;IAEpE;;;;OAIG;IACI,QAAQ,CAAC,KAAY,EAAE,MAAc;QAExC,MAAM,GAAG,GAAG,IAAI,CAAC,QAAQ,CAAC,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC,CAAC;QAClD,MAAM,UAAU,GAAG,IAAI,CAAC,QAAQ,CAAC,SAAS,CAAC,MAAM,CAAC,CAAC;QACnD,IAAI,KAAK,GAAU,KAAK,CAAC;QACzB,IAAI,GAAG,GAAU,KAAK,CAAC;QAEvB,QAAQ;QACR,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EAC/B,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,aAAa,EAAE,CAAC,KAAK,CAAC;YAClC,GAAG,GAAG,GAAG,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC;QAClC,CAAC;QACD,MAAM;aACD,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EACpE,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC;YAChC,GAAG,GAAG,GAAG,CAAC,SAAS,EAAE,CAAC,KAAK,CAAC;QAChC,CAAC;QACD,KAAK;aACA,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EACpC,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,UAAU,EAAE,CAAC,KAAK,CAAC;YAC/B,GAAG,GAAG,GAAG,CAAC,QAAQ,EAAE,CAAC,KAAK,CAAC;QAC/B,CAAC;QACD,MAAM;aACD,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EACpC,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC;YAChC,GAAG,GAAG,GAAG,CAAC,SAAS,EAAE,CAAC,KAAK,CAAC;QAChC,CAAC;QACD,OAAO;aACF,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EACpC,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,YAAY,EAAE,CAAC,KAAK,CAAC;YACjC,GAAG,GAAG,GAAG,CAAC,UAAU,EAAE,CAAC,KAAK,CAAC;QACjC,CAAC;QACD,MAAM;aACD,IAAG,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,IAAI,UAAU,CAAC,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,EACpE,CAAC;YACG,KAAK,GAAG,GAAG,CAAC,WAAW,EAAE,CAAC,KAAK,CAAC;YAChC,GAAG,GAAG,GAAG,CAAC,SAAS,EAAE,CAAC,KAAK,CAAC;QAChC,CAAC;QAED,OAAO;YACH,IAAI,EAAE,KAAK;YACX,EAAE,EAAE,GAAG;SACV,CAAC;IACN,CAAC;8GA9DQ,iBAAiB,kBAGN,QAAQ;kHAHnB,iBAAiB,cADL,MAAM;;2FAClB,iBAAiB;kBAD7B,UAAU;mBAAC,EAAC,UAAU,EAAE,MAAM,EAAC;;0BAIf,MAAM;2BAAC,QAAQ","sourcesContent":["import {Inject, Injectable} from '@angular/core';\n\nimport {DateTimeValue} from '../../interfaces/dateTime/datetime.interface';\nimport {DATE_API} from '../../misc/tokens';\nimport {DateApi} from '../dateApi/dateApi.interface';\n\n/**\n * Class used for obtaining DateTimeValue for various formats\n */\n@Injectable({providedIn: 'root'})\nexport class DateValueProvider<TDate = unknown>\n{\n    //######################### constructor #########################\n    constructor(@Inject(DATE_API) protected _dateApi: DateApi<TDate>)\n    {\n    }\n\n    //######################### public methods #########################\n\n    /**\n     * Gets DateTimeValue from single value based on format\n     * @param value - Current value to be converted to ranged value\n     * @param format - Format that is requested to be displayed, it tells what range should be created\n     */\n    public getValue(value: TDate, format: string): DateTimeValue<TDate>\n    {\n        const val = this._dateApi.getValue(value, format);\n        const fullFormat = this._dateApi.getFormat(format);\n        let start: TDate = value;\n        let end: TDate = value;\n\n        //minute\n        if(fullFormat.indexOf('m') >= 0)\n        {\n            start = val.startOfMinute().value;\n            end = val.endOfMinute().value;\n        }\n        //hour\n        else if(fullFormat.indexOf('H') >= 0 || fullFormat.indexOf('h') >= 0)\n        {\n            start = val.startOfHour().value;\n            end = val.endOfHour().value;\n        }\n        //day\n        else if(fullFormat.indexOf('d') >= 0)\n        {\n            start = val.startOfDay().value;\n            end = val.endOfDay().value;\n        }\n        //week\n        else if(fullFormat.indexOf('w') >= 0)\n        {\n            start = val.startOfWeek().value;\n            end = val.endOfWeek().value;\n        }\n        //month\n        else if(fullFormat.indexOf('M') >= 0)\n        {\n            start = val.startOfMonth().value;\n            end = val.endOfMonth().value;\n        }\n        //year\n        else if(fullFormat.indexOf('Y') >= 0 || fullFormat.indexOf('y') >= 0)\n        {\n            start = val.startOfYear().value;\n            end = val.endOfYear().value;\n        }\n\n        return {\n            from: start,\n            to: end,\n        };\n    }\n}\n"]}

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@anglr/datetime",
-    "version": "9.0.2",
+    "version": "9.0.3-beta.20260518114213",
     "description": "Angular library for datetime manipulation components",
     "type": "module",
     "sideEffects": false,