Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Dynamic Key/Value Field Component for Edit Contentlet #30493

Open
Tracked by #25445
oidacra opened this issue Oct 29, 2024 · 1 comment
Open
Tracked by #25445

Implement Dynamic Key/Value Field Component for Edit Contentlet #30493

oidacra opened this issue Oct 29, 2024 · 1 comment

Comments

@oidacra
Copy link
Member

oidacra commented Oct 29, 2024

Parent Issue

#25445

User Story

As a content editor, I want to be able to manage dynamic key/value pairs in the Edit Contentlet interface, so I can efficiently organize and maintain structured data with flexible key-value relationships.

Acceptance Criteria

  1. Dynamic Field Management

    • Users can add unlimited key/value pairs
    • New entries appear at the top of the list
    • Maximum 6 pairs shown per page with pagination
    • Must use PrimeNG table component for display
  2. Validation Requirements

    • Both key and value fields must be filled before adding a new pair
    • Display error message if user attempts to add new line with empty fields
    • Support for custom validations defined in content type configuration
  3. UI/UX Features

    • Drag and drop functionality for reordering pairs
    • Delete icon/button for removing individual pairs
    • Clear visual indication of required fields
    • Implement the visual style of the Figma File
  4. Pagination

    • Implement PrimeNG pagination when more than 6 pairs exist
    • Clear indication of total pairs and current page
    • Smooth navigation between pages

Proposed Objective

Technical User Experience

Proposed Priority

Priority 2 - Important

External Links

CleanShot 2024-10-29 at 16 00 52@2x

Figma File

Assumptions & Initiation Needs

Quality Assurance Notes & Workarounds

Test Cases to Consider:

  1. Adding/removing pairs
  2. Drag and drop reordering
  3. Pagination navigation
  4. Validation scenarios
  5. Required field handling
  6. Performance with large datasets
@oidacra oidacra moved this from New to Next 1-3 Sprints in dotCMS - Product Planning Oct 29, 2024
@oidacra oidacra added the Epic label Oct 29, 2024
@oidacra oidacra changed the title Implement Key/Value Field Implement Dynamic Key/Value Field Component for Edit Contentlet Oct 29, 2024
@oidacra oidacra removed the Epic label Oct 29, 2024
@oidacra
Copy link
Member Author

oidacra commented Nov 6, 2024

No will be implemented the new design.

@oidacra oidacra moved this from Next 1-3 Sprints to Future in dotCMS - Product Planning Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Future
Development

No branches or pull requests

1 participant