Relationship Field: Enable Static Fields for Search #31127
Assignees
Comments
john-thomas-dotcms
moved this from Current Sprint Backlog
to Next 1-3 Sprints
in dotCMS - Product Planning
nicobytes
moved this from Next 1-3 Sprints
to Current Sprint Backlog
in dotCMS - Product Planning
nicobytes
moved this from Current Sprint Backlog
to In Progress
in dotCMS - Product Planning
3 tasks
3 tasks
github-merge-queue bot
pushed a commit
that referenced
this issue
Jan 29, 2025
…ps field (#31253) ### Parent Issue #31127 ### Proposed Changes This pull request introduces a new `LanguageFieldComponent` for selecting languages in a dropdown menu. It includes the component's implementation, its associated store for managing state, and comprehensive unit tests for both the component and the store. ### New Component and Store Implementation: * **Component Implementation:** * [`language-field.component.html`](diffhunk://#diff-289b326ca1d3fb195cb055beb5a07955c766ec5aa2761d14eedb82157f13ea41R1-R25): Added HTML template for the language dropdown, including labels, dropdown options, and error handling. * [`language-field.component.ts`](diffhunk://#diff-b2823342540a7c0292f57c8d819bd0773c84ad3b7566326c4b774de0efb819c9R1-R153): Defined the `LanguageFieldComponent` with Angular's `ControlValueAccessor` and `OnInit` interfaces, including methods for handling language selection and form control integration. * **Store Implementation:** * [`language-field.store.ts`](diffhunk://#diff-93465d0e2e8c53c6ea29833386b45327bbf786e1092fafd7bd39810c4caa493dR1-R123): Created `LanguageFieldStore` using NgRx signals for state management, including methods for loading languages, selecting a language, and handling errors. ### Unit Tests: * **Component Tests:** * [`language-field.component.spec.ts`](diffhunk://#diff-70b9782af3524885226aa3243cd83a66a28180c4c6bec5ac4974ba7484a836afR1-R198): Added unit tests for the `LanguageFieldComponent`, covering initialization, value writing, change handling, and edge cases. * **Store Tests:** * [`language-field.store.spec.ts`](diffhunk://#diff-418e6f29da1c71c019f43d84961c9eefb3632494cd66da8f4dcff38f35449ee3R1-R147): Added unit tests for the `LanguageFieldStore`, covering initial state, state management, language selection, error handling, and reset functionality. ### Checklist - [x] Tests - [x] Translations - [x] Security Implications Contemplated (add notes if applicable)
github-project-automation
bot
moved this from In Progress
to Done
in dotCMS - Product Planning
github-project-automation
bot
moved this from In Progress
to Current Sprint Backlog
in dotCMS - Product Planning
nicobytes
moved this from Current Sprint Backlog
to In Progress
in dotCMS - Product Planning
This was referenced Jan 31, 2025
nicobytes
moved this from In Progress
to Current Sprint Backlog
in dotCMS - Product Planning
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Parent Issue
#30495
Task
Currently, the Relationship Field in our system allows dynamic fields. However, this feature enhancement aims to enable specific static fields to be consistently searchable. The following fields should always be enabled for search:
This improvement will ensure that these fields are universally accessible for search, enhancing usability and consistency.
Proposed Objective
User Experience
Proposed Priority
Please Select
Acceptance Criteria
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Figma Link: https://www.figma.com/design/YMTdSO5gKf18rc1pCCv1jN/Edit-Content-Screen?node-id=3891-57296&t=6MCYZtEJxamL6JFW-1
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: