@skysoftware-co/bayan-core-widgets-ui 0.0.8 → 0.0.10

package/.github/copilot/WidgetProjectStructure.md

@@ -1,81 +0,0 @@
-Bayan Core Widgets Project Structure & Widget Creation Guide
-Project Structure Overview
-This repository is organized as follows:
-
-Bayan.Core.Widgets/
-├── projects/
-│   └── namespace-ui/
-│       ├── README.md
-│       ├── src/
-│       │   └── lib/
-│       │       ├── <widget-name>/
-│       │       │   ├── <widget-name>.component.ts
-│       │       │   ├── <widget-name>.component.html
-│       │       │   ├── <widget-name>.component.scss
-│       │       │   └── ...
-│       │       └── shared/
-│       │           ├── <feature>.dtos.ts
-│       │           └── <feature>.service.ts
-│       └── ...
-├── README.md
-└── ...
-
-•	Each widget is a standalone Angular component under `projects/namespace-ui/src/lib/<widget-name>/`.
-•	Reusable DTOs and services shared by multiple widgets belong under `projects/namespace-ui/src/lib/shared/`.
-•	Reuse shared services and pipes exported by `@skysoftware-co/sky-components-ui` before adding new ones under the Widgets project.
-•	Do not create Widgets-local services named `CookiesService`, `SecureCookieService`, `SecureStorageService`, `LocalStorageService`, `EncryptionService`, `TranslationService`, `SkyScreenService`, or `SkyPDFService`; import them from `@skysoftware-co/sky-components-ui`.
-•	Do not create Widgets-local pipes named `capitalizefirst`, `highlight`, `safe`, or `translate`; import them from `@skysoftware-co/sky-components-ui`.
-•	Documentation for this library belongs at `projects/namespace-ui/README.md`.
----
-
-How to Create a New Widget
-1. Generate a New Standalone Component
-From the root of the repository, run:
-ng generate component <widget-name> --project namespace-ui --standalone
-
-This creates a new folder and component files under `projects/namespace-ui/src/lib/<widget-name>/`
-
-2. (Optional) Reuse Existing Shared Services Or Pipes First
-If your widget needs API, translation, formatting, or shared infrastructure behavior, first import the exported service or pipe from `@skysoftware-co/sky-components-ui`.
-
-Create a new Widgets-local service only if the package does not already provide the required behavior.
-Never create local replacements for `CookiesService`, `SecureCookieService`, `SecureStorageService`, `LocalStorageService`, `EncryptionService`, `TranslationService`, `SkyScreenService`, `SkyPDFService`, `capitalizefirst`, `highlight`, `safe`, or `translate`.
-If the new DTO or service will be reused by more than one widget, create it under `projects/namespace-ui/src/lib/shared/` instead of the widget folder.
-
-3. Implement the Widget
-•	Use @Input() for all configurable properties.
-•	Use @Output() for all events.
-•	Use the shared translation pipes exported by `@skysoftware-co/sky-components-ui` for all user-facing text.
-•	Use shared services from `@skysoftware-co/sky-components-ui` when available, otherwise use a Widgets-specific service with baseUrl as an input.
-•	Emit loading and error states via isLoadingChanged and errorOccurred outputs.
-•	Keep widget-private files inside the widget folder.
-•	Keep reusable shared DTOs and services in `src/lib/shared/`.
-4. Add the Widget to the Module (if needed)
-If you are not using standalone components, declare your widget in the appropriate module. For standalone, this is not required.
-5. Follow Naming and Code Standards
-•	Component selector: hr-<widget-name>
-•	Folder and file names: kebab-case
-•	Class names: PascalCase
-•	Inputs/Outputs: camelCase
-6. Test and Document
-•	Add unit tests in the same folder as your component.
-•	Document all inputs, outputs, and usage in `projects/namespace-ui/README.md` unless the user explicitly requests another documentation location.
----
-Example: Creating a "profile-job-info-contract-widget"
-1.	Generate the component:
-   ng generate component profile-job-info-contract-widget --project namespace-ui --standalone
-   
-2.	Import and reuse the required shared service or pipe from `@skysoftware-co/sky-components-ui` when available.
-   
-3.	Implement as per standards above.
-
-
----
-Additional Tips
-•	Review existing widgets in `projects/namespace-ui/src/lib/` for reference.
-•	Use the provided services and pipes from `@skysoftware-co/sky-components-ui` before adding new Widgets-specific implementations.
-•	Keep widgets focused and reusable.
-•	If another repo is mentioned as a source example, treat it as reference-only unless the user explicitly asks to edit it.
----
-For more details, see the main ./README.md and the Widget Development Guide.
----

package/.github/copilot/git.md

@@ -1,176 +0,0 @@
-## Version Control
-
-This document defines the standards and conventions used in Git version control. All developers and AI assistants should follow these guidelines to maintain consistency across the codebase.
-
-### Commit Message Format
-
-```
-<type>(<scope>): <subject>
-
-Types: feat, fix, docs, refactor, test, chore
-Examples:
-- feat(policy): add premium rule validation
-- fix(employee): correct service years calculation
-```
-
-### Branch Naming
-
-```
-feature/add-dependant-enrollment
-bugfix/fix-premium-calculation
-hotfix/correct-membership-id-generation
-refactor/improve-error-handling
-docs/update-api-documentation
-```
-
-### .gitignore Configuration
-
-Every .NET repository MUST have a `.gitignore` file in the repository root. When creating new projects, always create this file with the standard configuration below.
-
-**Create file:** `.gitignore` (repository root)
-
-**Essential exclusions:**
-- Build outputs (`bin/`, `obj/`)
-- IDE files (`.vs/`, `.vscode/`, `.idea/`)
-- User-specific files (`*.suo`, `*.user`)
-- NuGet packages (`packages/`, `*.nupkg`)
-- Sensitive files (`appsettings.Development.json`, `*.pfx`, `.env`)
-- Test results (`TestResults/`, `*.trx`)
-- OS-specific files (`Thumbs.db`, `.DS_Store`)
-
-**Complete .gitignore template:**
-
-```gitignore
-# .NET Build Outputs
-[Bb]in/
-[Oo]bj/
-[Ll]og/
-[Ll]ogs/
-
-# Visual Studio 2022/2019/2017 cache/options
-.vs/
-*.suo
-*.user
-*.userosscache
-*.sln.docstates
-
-# Visual Studio Code
-.vscode/*
-!.vscode/settings.json
-!.vscode/tasks.json
-!.vscode/launch.json
-!.vscode/extensions.json
-*.code-workspace
-
-# Build results
-[Dd]ebug/
-[Dd]ebugPublic/
-[Rr]elease/
-[Rr]eleases/
-x64/
-x86/
-[Ww][Ii][Nn]32/
-[Aa][Rr][Mm]/
-[Aa][Rr][Mm]64/
-bld/
-
-# .NET Core
-project.lock.json
-project.fragment.lock.json
-artifacts/
-
-# NuGet Packages
-*.nupkg
-*.snupkg
-**/packages/*
-!**/packages/build/
-*.nuget.props
-*.nuget.targets
-
-# Test Results
-[Tt]est[Rr]esult*/
-[Bb]uild[Ll]og.*
-*.trx
-*.coverage
-*.coveragexml
-TestResults/
-
-# Visual Studio profiler
-*.psess
-*.vsp
-*.vspx
-*.sap
-
-# ReSharper
-_ReSharper*/
-*.[Rr]e[Ss]harper
-*.DotSettings.user
-
-# JetBrains Rider
-*.sln.iml
-.idea/
-
-# SQL Server files
-*.mdf
-*.ldf
-*.ndf
-
-# Sensitive configuration files
-appsettings.Development.json
-appsettings.Local.json
-*.secrets.json
-connectionstrings.json
-*.pfx
-*.p12
-
-# AWS credentials
-credentials
-config
-
-# Environment files
-.env
-.env.local
-.env.*.local
-
-# macOS
-.DS_Store
-
-# Windows
-Thumbs.db
-Desktop.ini
-$RECYCLE.BIN/
-*.lnk
-
-# Logs and databases
-*.log
-*.sqlite
-*.sqlite3
-
-# Temporary files
-*.tmp
-*.temp
-*.swp
-*~
-
-# Coverage reports
-coverage/
-
-# Terraform
-*.tfstate
-*.tfstate.*
-.terraform/
-
-# Docker
-docker-compose.override.yml
-```
-
-**Why this matters:**
-- Prevents committing build artifacts and generated files
-- Protects sensitive configuration and credentials
-- Keeps repository clean and reduces merge conflicts
-- Ensures consistent behavior across development environments
-
-**When to create:**
-- ✅ ALWAYS create `.gitignore` as first file in new repository
-- ✅ Before first `git add` command
-- ✅ When setting up new .NET solution

package/.github/copilot/guideline.md

@@ -1,466 +0,0 @@
-
-# Bayan HRMS — AI Design & Development Prompt Guide
-
-This document defines the complete rules for generating UI designs and Angular components for Bayan HRMS using AI tools such as Figma Make, design copilots, or code generators.
-
-The AI MUST follow these rules strictly when generating any screen, component, or UI layout.
-
-This guideline is the single source of truth for:
-- UI Design
-- UX Structure
-- Design Tokens
-- Angular Implementation
-- Component Architecture
-
----
-
-# 1. Product Design Philosophy
-
-All UI generated must follow these product values.
-
-## Core Principles
-
-1. Clarity over cleverness  
-   HR systems are used daily. Reduce cognitive load.
-
-2. Consistency builds trust  
-   Use the same patterns everywhere.
-
-3. Scalability  
-   UI must work for small companies and enterprise hospitality groups.
-
-4. Respect user time  
-   Interfaces should feel fast and purposeful.
-
----
-
-# 2. UX Guidelines
-
-AI must follow these UX rules:
-
-- Layouts must be task-first
-- Use progressive disclosure for advanced options
-- Avoid visual clutter
-- Always provide clear system feedback
-
----
-
-# 3. Layout System
-
-## Frame Sizes
-
-Desktop: 1440px  
-Extended detail screens: 1460px  
-Tablet: 1024px  
-Mobile: 375px (reference only)
-
-## Grid System
-
-- 12 column grid
-- Margin: 80px
-- Content margin: 32px
-- Gutter: 24px
-
----
-
-# 4. Spacing System
-
-Use the 8px spacing scale.
-
-Allowed values:
-4, 8, 16, 24, 32, 40, 48, 64
-
-Typical usage:
-
-- Tight spacing: 4px
-- Component spacing: 8px
-- Standard gaps: 16px
-- Section spacing: 32px
-- Page margins: 48px
-
----
-
-# 5. Color System
-
-AI must only use colors from this palette.
-
-## Primary Colors
-
-Primary Orange: #F18206  
-Link Orange: #F78204  
-Secondary Beige: #F0E4D5  
-Teal Accent: #00796B
-
-Usage:
-
-- #F18206 → Primary actions
-- #F78204 → Links
-- #00796B → Action icons
-- #F0E4D5 → Badges
-
-## Neutral Colors
-
-Background Primary: #FFFFFF  
-Background Secondary: #FAFAFA  
-Background Tertiary: #F5F5F5  
-Text Primary: #333333  
-Text Tertiary: #212529
-
-Important rule:
-
-Never use grey text like #9D9C9C.
-
-Muted text must be:
-#333333 with font-weight 300.
-
----
-
-# 6. Status Colors
-
-Accepted: #F18206  
-Assigned: #F3C94B  
-Assessed: #3B82F6  
-Reviewed: #388E3C
-
-Additional semantic colors:
-
-Error: #EF4444  
-Warning: #F59E0B  
-Neutral: #9CA3AF
-
----
-
-# 7. Typography
-
-Font family: Inter
-
-## Typography Scale
-
-H1 — 32px Bold  
-H2 — 22px Medium  
-H3 — 16px Semibold  
-Body Large — 16px Regular  
-Body — 14px Regular  
-Small — 12px Regular  
-Caption — 10px Regular
-
-## Typography Rules
-
-- Only one H1 per screen
-- Maintain hierarchy with size and weight
-- Minimum line height 1.4
-- Text must be left aligned in forms and tables
-
----
-
-# 8. Border Radius
-
-Cards: 12px  
-Buttons: 7px  
-Inputs: 5px  
-Badges: 4px  
-Circles: 50%
-
----
-
-# 9. Shadows
-
-Standard card shadow:
-
-0px 4px 4px rgba(0,0,0,0.25)
-
-Rules:
-
-- Cards use shadow
-- Buttons do not use shadow
-- Elevated components use card shadow
-
----
-
-# 10. Component Design Rules
-
-## Buttons
-
-Primary Button
-- Background: #F18206
-- Text: White
-- Height: 36px
-- Radius: 7px
-
-Secondary Button
-- Background: White
-- Border: #C9C7C7
-- Height: 36px
-- Radius: 7px
-
-## Cards
-
-Background: White  
-Border: rgba(224,224,224,0.78)  
-Radius: 12px  
-Shadow: Standard card shadow  
-Padding: 16px
-
-## Tables
-
-Header
-- Background: #F2F2F2
-- Height: 32px
-- Text: 12px semibold
-
-Rows
-- Height: 40–60px
-- Padding: 16px
-
-## Inputs
-
-Background: #F8F7F7  
-Border: rgba(0,0,0,0.23)  
-Height: 36–48px  
-Radius: 5px  
-Padding: 16px
-
-## File Upload
-
-Height: 220px  
-Border: dashed  
-Radius: 5px
-
----
-
-# 11. Navigation
-
-Primary navigation
-- Left sidebar
-- Collapsible
-- Background #FAFAFA
-
-Top bar
-- Height 148px
-- Background #F8F7F7
-
----
-
-# 12. Layout Patterns
-
-Dashboard Layout
-- Two column grid
-- Gap 24px
-- Equal card widths
-
-Detail Layout
-- Two panel layout
-- Main content left
-- Sidebar right (467px)
-
-Table Layout
-- Filters on top
-- Table full width
-- Pagination bottom
-
----
-
-# 13. Accessibility
-
-All UI must follow WCAG AA.
-
-Requirements:
-
-- Minimum contrast ratio
-- Visible focus states
-- Minimum click size 36px
-- Clear interactive affordance
-
----
-
-# 14. Data Handling
-
-Change tracking must display:
-
-New value  
-Old: [previous value]
-
-Old values must use font-weight 300.
-
----
-
-# 15. Empty States
-
-Empty states must:
-
-- Explain why content is empty
-- Provide next action
-- Never blame the user
-
----
-
-# 16. Angular Implementation Rules
-
-Angular version: v19+
-
-## Styling
-
-Use Bootstrap 5
-
-Install:
-bootstrap ^5.3.3
-
-Rules:
-
-- Use one global style.css
-- Do not create component CSS files
-- Avoid inline styles
-
-Use:
-class, ngClass, ngStyle
-
----
-
-# 17. Icons
-
-Use FontAwesome packages:
-
-@fortawesome/angular-fontawesome  
-@fortawesome/fontawesome-svg-core  
-@fortawesome/pro-light-svg-icons  
-@fortawesome/pro-regular-svg-icons  
-@fortawesome/pro-solid-svg-icons  
-@fortawesome/pro-thin-svg-icons
-
----
-
-# 18. UI Components
-
-Never use native HTML controls.
-
-Always use DevExtreme components.
-
-Packages:
-
-devextreme 24.1.7  
-devextreme-angular 24.1.7
-
----
-
-# 19. Component Architecture
-
-Rules:
-
-- Each component must have a single responsibility
-- Split complex screens into subcomponents
-- Use standalone components
-
-Use:
-
-Input  
-Output  
-Signals
-
-Do not define interfaces inside components.
-
-Use folders:
-
-/types  
-/api  
-/services
-
----
-
-# 20. Routing
-
-Use lazy loading.
-
-Load pages only when needed.
-
----
-
-# 21. Shared Packages
-
-Use:
-
-@skysoftware-co/bayan-components-ui  
-@skysoftware-co/sky-components-ui
-
-Theme:
-
-@skysoftware-co/sky-themes
-
----
-
-# 22. Date Handling
-
-Use moment ^2.30.1
-
----
-
-# 23. File Structure
-
-Angular components must include only:
-
-.ts  
-.html
-
-Do not create:
-
-.spec.ts  
-.css  
-.scss
-
----
-
-# 24. Responsiveness
-
-Designs must support:
-
-Desktop  
-Large Desktop  
-Tablet
-
-Mobile is optional reference.
-
----
-
-# 25. Naming Conventions
-
-Component naming pattern:
-
-Component / Type / State
-
-Examples:
-
-Button/Primary/Default  
-Card/Employee/Default  
-Table/Status/Compact
-
----
-
-# 26. Development Checklist
-
-Before finalizing UI or code verify:
-
-✓ Approved colors used  
-✓ Spacing scale applied  
-✓ Inter font used  
-✓ Correct border radius  
-✓ Card shadows applied  
-✓ WCAG contrast respected  
-✓ Click targets ≥ 36px  
-✓ Proper component architecture
-
----
-
-# 27. Critical AI Rules
-
-AI must:
-
-1. Follow the design system strictly
-2. Never invent colors or spacing values
-3. Always use DevExtreme components
-4. Follow Angular architecture rules
-5. Maintain consistent typography and spacing
-6. Generate responsive layouts
-7. Use Bootstrap utility classes
-
----
-
-End of Guideline