# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.2.1-pl] - 2026-09-24

### Changed
- Modx theme follows the MODX 3 manager more closely (#46): a Button with no severity uses the green `.primary-button` fill (`#6CB24A`), same as `severity="success"`; navy `#234368` stays on tabs, links and selection
- Modx theme: single-line fields are 32px (`modx.field.height`), buttons stay 36px (`modx.control.height`) (#46)
- Modx theme: ToggleSwitch, Slider, ProgressBar, Checkbox, RadioButton, DatePicker, Dialog, DataTable, Paginator, Tabs, Tooltip, Toast and menus restyled to the manager (#46)
- DEVELOPER_GUIDE: version-aware VueTools check for theming consumers (#25)
- GitHub issue and pull request templates (#45)

### Fixed
- Modx theme: DatePicker, Slider and ProgressBar light overrides follow `darkModeSelector`, including a `.p-dark` subtree (#48)
- Line endings normalized to LF via `.gitattributes` (#48)

## [1.2.0-pl] - 2026-09-14

### Added
- Native MODX 3 manager theme `Modx` for PrimeVue 4 (Nora base, splash `#234368`, 3px radius, 13px body)
- Helpers `ModxManagerTheme` (`darkModeSelector: 'none'`) and `ModxTheme` (class `.p-dark`)
- Centralized theming (#22): system setting `vuetools.theme` (default `aura`), `window.VueTools` injection, `@vuetools/useTheme` / `getActiveTheme()` with Aura fallback
- Preset registry (`aura`, `modx`) inside VueTools; new themes register only here
- Import Map aliases `vuetools` and `vuetools/theme` (same bundle as `primevue`; `vuetools/theme` is the version-aware theming signal)
- Theme showcase: `npm run demo` / `npm run build:demo` (`src/demo/`, `vite.config.demo.js`)
- Asset `?v=` cache-bust via filemtime for vendor/composables
- System setting combo `vuetools-combo-theme` (`aura` | `modx`) for `vuetools.theme`

### Fixed
- One VueTools service under both `vuetools` and `vueTools` keys, so Import Map and CSS are not registered twice (#11)

### Changed
- README and DEVELOPER_GUIDE: prefer `getActiveTheme()`; Save = `severity="success"`; token layers
- Backward compatible: extras that hardcode `Aura` / `ModxManagerTheme` keep working unchanged

### Security
- Consolidated build dependency bumps: `vite`, `postcss`, `nanoid`, `brace-expansion` (#21)

## [1.1.2-pl] - 2026-06-15

### Added
- `VueTools\Service` class so MODX resolves the `vuetools` service via the conventional `model/vuetools/` path (#6)

### Changed
- Migrated PrimeVue theme package `@primevue/themes` to the maintained `@primeuix/themes` (#9)
- Updated bundled stack: Vue 3.5.32, Pinia 3.0.4, PrimeVue 4.5.5; `primelocale` ^2.3.1 (#9)
- Synced hardcoded `$versions` in `VueCore` with the shipped bundles (#13)
- Bumped `postcss` to 8.5.15 — includes security fixes (#12)

## [1.1.1-pl] - 2026-02-10

### Fixed
- Missing `usePrimeVueLocale.min.js` file in build

### Changed
- Updated dependencies

## [1.1.0-pl] - 2026-02-05

### Added
- PrimeVue localization: composable `usePrimeVueLocale` and locale presets (de, en, es, fr, pl, ru, uk)
- `getPrimeVueLocale(cultureKey?)` returns PrimeVue locale for DataTable filters, DatePicker, Calendar; uses `MODx.cultureKey` when cultureKey omitted
- Locales from [primelocale](https://github.com/primefaces/primelocale) package (dependency added)
- Import Map: `@vuetools/usePrimeVueLocale` entry
- DEVELOPER_GUIDE section "Локализация PrimeVue" and README usage example

## [1.0.1-pl] - 2026-01-01

First beta release.

### Added
- Vue 3.5.13 bundled as ES module
- Pinia 3.0.1 bundled as ES module
- PrimeVue 4.3.1 with Aura theme bundled as ES module
- PrimeIcons 7.0.0 included
- Import Map registration for browser module resolution
- CSS isolation with `.vueApp` prefix (no conflicts with ExtJS)
- Composables: useApi, useLexicon, useModx, usePermission
- VueCoreManager plugin for automatic Import Map registration

### Changed
- Renamed from ModxProVueCore to VueTools
