Skip to content

[feat] Add EventExtract component with multi-region service extraction and form enhancements #168

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

Closed
wants to merge 6 commits into from

Conversation

Aloento
Copy link
Member

@Aloento Aloento commented May 20, 2025

Summary of the Pull Request:

This pull request introduces a comprehensive set of enhancements centered around service extraction and event management, aimed at improving user experience, interactivity, and code reliability.
image

  1. EventExtract Component Integration:

    • A new EventExtract modal component allows users to extract services related to an event.
    • Enables service selection via a dynamic and user-friendly table interface.
    • Conditionally rendered within EventCard when multiple region services are associated with an event.
  2. Enhanced UI Interaction:

    • Validates service selections to ensure at least one item is chosen before proceeding.
    • Provides real-time user feedback to guide interaction within the modal.
  3. Custom Hook for Service Extraction:

    • Implements a dedicated custom hook to manage service state, form validation, and async API interactions.
    • Ensures seamless navigation to the newly created event upon successful service extraction.
  4. Token Validation and Form Submission Improvements:

    • Fixes an issue related to setStart() in the token validation logic to ensure correct form behavior.
    • Adds a Refresh method to the context provider, offering better state control and context management.

Aloento added 5 commits May 20, 2025 16:17
Introduces the EventExtract component, allowing users to extract services related to an event through a modal interface.

Implements a table for displaying and selecting services, improving user interaction.

Validates selections and provides user feedback, enhancing the overall functionality and usability of the event management feature.
Corrects the call to `setStart()` in the token validation logic to ensure proper functionality during form submission.

Adds a `Refresh` method to the context provider, enhancing the context's capability for state management.

Improves code clarity and reliability in handling form data.
Implements a new custom hook that facilitates the extraction of services related to a specific event.

This hook manages service states, validates inputs, and handles asynchronous requests to a backend API for processing event data.

It enhances user interaction by ensuring at least one service is selected before proceeding with the extraction and provides navigation to the newly created event upon successful extraction.
Introduces the EventExtract component within the EventCard to handle scenarios where events are associated with multiple region services.

This enhances the UI by conditionally rendering the EventExtract when more than one region service is present, improving user experience and clarity in event details.
@Aloento Aloento self-assigned this May 20, 2025
@Aloento Aloento changed the title feat: Add EventExtract component with multi-region service extraction and form enhancements [feat] Add EventExtract component with multi-region service extraction and form enhancements May 20, 2025
@Aloento Aloento linked an issue May 20, 2025 that may be closed by this pull request
# Conflicts:
#	package.json
#	pnpm-lock.yaml
@Aloento Aloento closed this May 29, 2025
@Aloento Aloento deleted the feat branch May 29, 2025 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add functionality for extracting a component to a new incident
1 participant