Remove pagination and search functionality from regency selection as they're not needed in this context. Replace ComboboxPaginated with simpler Combobox component and adjust useRegencies composable options accordingly.
feat: implement postal region model and update address handling
- Add new PostalRegion model and service
- Replace postalCode with postalRegion in address-related components
- Update schemas and models to use locationType_code consistently
- Add usePostalRegion composable for postal code selection
- Modify patient form to handle address changes more robustly
feat(patient): add ID column and improve date formatting
- Add patient ID column to patient list
- Format dates using 'id-ID' locale in preview
- Update identity number display for foreign patients
- Include passport number for foreign nationals
* fix: adjustment some schemas
* fix(room): fixing integrate unit of room
* feat(warehouse): modify form and integration
* feat(counter): modify form and integration
* feat(screen): add list, form and integration
* feat(screen): add page for public screen
* fix: add on reset state at list
* fix: solve list of relation
* feat(chamber): integrate form to api chamber
* feat(bed): integrate form to api bed
* fix: add searching function on list service
* fix: rewrite style for dropdown and tree select
* fix: add sort params
* fix: add sort params on division + medicine
* feat(division-position): layouting form + list
* fix: add sort params for getValueList
* chore: modify side menu style
* chore: fix ui dashboard
* feat(division-position): add content list
* feat(division-position): add temporary page
* feat(division-position): modify content and entry form
Use the centralized relationshipCodes constant from lib/constants instead of maintaining a duplicate list of options. This improves maintainability and ensures consistency across the application.
Update interface name from PatientEntity to Patient for better clarity and consistency. Modify all related components and models to use the new interface name. Also includes minor improvements to address handling in patient forms.
- Add preload relationships to address-related models
- Rename postalCode to postalCode_code for consistency
- Simplify location type handling with hidden fields
- Update validation schemas and form components
- Improve address display in patient preview
Move address, contact and relative data into nested properties of Person model
Update preview component to access data through person object
Remove separate props for addresses, contacts and relatives
Add callback URL parameter to redirect after successful patient creation. The URL can be passed via 'return-path' query parameter and will include the created patient's ID. This enables seamless integration with external systems that need to handle post-creation flows.
Update all references to postal_code field to use camelCase postalCode for consistency with codebase naming conventions. This includes changes to models, schemas, and components.
- Replace hardcoded job options with dynamic list from constants
- Update patient preview to display occupation by code if available
- Expand occupation codes in constants with comprehensive list
- Standardize parameter naming with hyphens instead of underscores
- Remove page size limit and enable no-limit flag for all region queries
- Improve arrow function syntax consistency and formatting
feat(patient): add newborn status field and validation
- Add radio button component for newborn status selection
- Update patient schema with newborn status validation
- Remove deprecated alias field from person model
- Refactor disability type handling in patient schema
fix(patient): correct address comparison logic and schema
Update the patient address comparison to use boolean instead of string '1' and modify the schema to transform the string value to boolean. This ensures consistent type usage throughout the application.
feat(models): add village and district model interfaces
Add new model interfaces for Village and District with their respective generator functions. These models will be used to handle administrative division data in the application.
feat(address): implement dynamic province selection with caching
- Add province service for CRUD operations
- Create useProvinces composable with caching and loading states
- Update select-province component to use dynamic data
- Export SelectItem interface for type consistency
- Improve combobox styling and accessibility
feat(address-form): implement dynamic regency selection with caching
- Add new regency service for CRUD operations
- Create useRegencies composable with caching and loading states
- Update SelectRegency component to use dynamic data based on province selection
- Improve placeholder and disabled state handling
feat(address-form): implement dynamic district selection
- Add district service for CRUD operations
- Create useDistricts composable with caching and loading states
- Update SelectDistrict component to use dynamic data
- Remove hardcoded district options and implement regency-based filtering
feat(address-form): implement dynamic village selection with caching
- Add village service for CRUD operations
- Create useVillages composable with caching and loading states
- Update SelectVillage component to fetch villages based on district
- Remove hardcoded village options in favor of API-driven data
feat(address-form): improve address selection with debouncing and request deduplication
- Add debouncing to prevent rapid API calls when selecting addresses
- Implement request deduplication to avoid duplicate API calls
- Add delayed form reset to ensure proper composable cleanup
- Add isUserAction flag to force refresh when user changes selection
