* feat(profile): implement local hooks for profile and service data editing - Added `useProfileEdit` and `useServiceEdit` hooks to manage pending changes and save functionality for profile and service data cards. - Updated `ProfileDataCard` and `ServiceDataCard` components to utilize these hooks, enhancing user experience with save and cancel options. - Introduced buttons for saving and canceling changes, improving the overall interactivity of the forms. - Refactored input handling to use `updateField` for better state management. * feat(bot): integrate Redis and update bot configuration - Added Redis service to both docker-compose files for local development and production environments. - Updated bot configuration to utilize the Grammy framework, replacing Telegraf. - Implemented graceful shutdown for the bot, ensuring proper resource management. - Refactored bot commands and removed deprecated message handling logic. - Enhanced environment variable management for Redis connection settings. - Updated dependencies in package.json to include new Grammy-related packages. * fix(registration): improve error handling for customer creation - Updated error handling in the registration feature to return a generic error message when documentId is not present, enhancing user experience by providing clearer feedback. * feat(bot): add unhandled command message and integrate unhandled feature - Introduced a new message for unhandled commands in Russian localization to improve user feedback. - Integrated the unhandled feature into the bot's middleware for better command handling. * feat(locales): update Russian localization with additional contact information - Enhanced the short description in the Russian localization file to include a contact note for user inquiries, improving user support accessibility. * feat(help): enhance help command with support information - Updated the help command to include a support message in the Russian localization, providing users with a contact point for inquiries. - Improved the command response by combining the list of available commands with the new support information, enhancing user experience. * fix(orders): update default sorting order for orders - Changed the default sorting order for orders from 'datetime_start:asc' to 'datetime_start:desc' to ensure the most recent orders are displayed first, improving the user experience in order management. * refactor(orders): remove ClientsOrdersList and streamline OrdersList component - Eliminated the ClientsOrdersList component to simplify the orders page structure. - Updated OrdersList to handle both client and master views, enhancing code reusability. - Improved order fetching logic and UI rendering for better performance and user experience. * fix(order-form): hide next button on success & error pages * refactor(bot): streamline bot middleware and improve key generator function - Removed unused session middleware and sequentialize function from the bot's error boundary. - Simplified the key generator function for rate limiting by condensing its implementation. - Enhanced overall code clarity and maintainability in the bot's configuration. * feat(customer): implement banned customer check and enhance customer data handling - Added `isCustomerBanned` function to determine if a customer is banned based on the `bannedUntil` field. - Updated the `BaseService` to throw an error if a banned customer attempts to access certain functionalities. - Enhanced the GraphQL operations to include the `bannedUntil` field in customer queries and mutations, improving data integrity and user experience. - Integrated the `CheckBanned` component in the layout to manage banned customer states effectively. * feat(ban-system): implement multi-level user ban checks across services - Added a comprehensive ban checking system to prevent access for banned users at multiple levels, including database, API, and client-side. - Introduced `bannedUntil` field in the customer model to manage temporary and permanent bans effectively. - Enhanced `BaseService` and various service classes to include ban checks, ensuring that banned users cannot perform actions or access data. - Updated error handling to provide consistent feedback for banned users across the application. - Improved user experience with a dedicated ban check component and a user-friendly ban notification page. * packages(apps/web): upgrade next@15.5.0
61 lines
1.8 KiB
TypeScript
61 lines
1.8 KiB
TypeScript
'use client';
|
|
|
|
import { BackButton } from './back-button';
|
|
import { ClientsGrid, MastersGrid } from './contacts-grid';
|
|
import { DateTimeSelect } from './datetime-select';
|
|
import { NextButton } from './next-button';
|
|
import { ErrorPage, SuccessPage } from './result';
|
|
import { ServicesSelect } from './services-select';
|
|
import { SubmitButton } from './submit-button';
|
|
import { useGetUrlData } from '@/hooks/url';
|
|
import { OrderStoreProvider, useInitOrderStore, useOrderStore } from '@/stores/order';
|
|
import { withContext } from '@/utils/context';
|
|
import { type OrderFieldsFragment } from '@repo/graphql/types';
|
|
import { LoadingSpinner } from '@repo/ui/components/ui/spinner';
|
|
import { type JSX } from 'react';
|
|
|
|
const STEP_COMPONENTS: Record<string, JSX.Element> = {
|
|
'client-select': <ClientsGrid />,
|
|
'datetime-select': <DateTimeSelect />,
|
|
error: <ErrorPage />,
|
|
'master-select': <MastersGrid />,
|
|
'service-select': <ServicesSelect />,
|
|
success: <SuccessPage />,
|
|
};
|
|
|
|
function getStepComponent(step: string) {
|
|
return STEP_COMPONENTS[step] ?? null;
|
|
}
|
|
|
|
const BUTTON_COMPONENTS: Record<string, JSX.Element | null> = {
|
|
'client-select': <NextButton />,
|
|
'datetime-select': <SubmitButton />,
|
|
error: null,
|
|
'master-select': <NextButton />,
|
|
'service-select': <NextButton />,
|
|
success: null,
|
|
};
|
|
|
|
function getButtonComponent(step: string) {
|
|
return BUTTON_COMPONENTS[step];
|
|
}
|
|
|
|
export const OrderForm = withContext(OrderStoreProvider)(function () {
|
|
const data = useGetUrlData<OrderFieldsFragment>();
|
|
|
|
useInitOrderStore(data);
|
|
|
|
const step = useOrderStore((store) => store.step);
|
|
if (step === 'loading') return <LoadingSpinner />;
|
|
|
|
return (
|
|
<div className="space-y-4 [&>*]:px-4">
|
|
{getStepComponent(step)}
|
|
<div className="space-y-2">
|
|
{getButtonComponent(step)}
|
|
<BackButton />
|
|
</div>
|
|
</div>
|
|
);
|
|
});
|