- Corrected the duplicated "Dashboard" text in the header.
- Verified and adjusted the webhook for sending financial alerts, ensuring it triggers on the specified days and times (Brazil timezone).
- Tested the webhook functionality with test accounts.
- Implement case-insensitive filtering for transaction types.
- Ensure NULL/empty categories are displayed as "Sem Categoria".
- Include categories with zero values in the results.
- Maintain month/year filtering.
- Ensure the output format matches the frontend's expectations.
- Modified `src/services/transacao/summaryService.ts` to address issues with the `getCategorySummary` endpoint.
- Implemented handling of NULL categories, transaction type filtering, and month/year filtering.
- Ensures the endpoint returns the correct category summaries, including "Sem Categoria" for NULL values, filtered by type and month/year.
Modified `src/services/transacao/summaryService.ts` to categorize transactions with NULL categories as "Despesas Sem Categoria" in the category summary.
Corrected the expense card on the dashboard to accurately reflect card expenses. Added month/year filter to the categories page. Verified and adjusted the category summary to ensure all transactions are included and correctly categorized.
- Fixed missing "Despesas" category in the pie chart.
- Re-added month/year filter to Dashboard and Transactions pages.
- Improved responsiveness of summary cards on smaller screens.
Added card deletion functionality. Improved card details display to show the month and the total expenses for each card. Fixed dashboard card layout issues on smaller screens. Separated expenses and credit card expenses in the dashboard summary.
This commit refactors the `src/pages/Index.tsx` file into smaller, more manageable components to improve code organization and readability. Unused imports and files will be removed.
- Implemented year-long view for "Receitas vs Despesas" chart.
- Improved dashboard card design and functionality, including navigation to filtered transactions on click.
- Verified the accuracy of the "Despesa por Categoria" chart.
- Replace the "Receitas vs Despesas" section with a chart.
- Ensure all expense categories are displayed in the "Gastos por Categoria" chart, and fix the color issue.
- Apply circular card styles with colors to the dashboard cards.
Removed the duplicate menu from the Dashboard, Transações, Cartões de Credito, Metas, Calendário, Conectar WhatsApp, and Grupos pages. Also removed the background effect from the Categorias page.
Replaced incorrect import of `authStore` with `useAuthStore` in `MeuCadastroForm.tsx`, `useProfileCompletion.ts`, and `CompleteProfile.tsx` to resolve TypeScript errors.
- Corrected import of `useAuthStore` in `src/App.tsx`, `src/components/avisos/ContaRecorrenteForm.tsx`, and `src/components/avisos/ContasRecorrentesList.tsx`.
- Added `children` prop to `ProtectedRoute` and `Layout` components in `src/App.tsx`.
- Fixed type error in `src/components/layout/Layout.tsx` related to `Sidebar` props.
Apply the SQL schema changes to create tables for recurring payment reminders, including tables for recurring accounts and sent reminders, along with necessary indexes and RLS policies.
Implemented a section on the landing page to showcase app usage with images representing audio, text, receipts, dashboard, and calendar views. Also added a background effect using the provided `background-paths.tsx` component and dependencies.
Review `src/pages/EmailConfirmation.tsx` and `src/components/auth/ProtectedRoute.tsx` to address email confirmation issues. Ensure the user is not considered logged in during email confirmation.
Corrected the email confirmation page to handle the token from the URL hash, authenticate the user, and display success/error messages. Added redirection to the dashboard after successful confirmation.
-edited src/pages/EmailConfirmation.tsx
Adjusted the login flow to redirect users to the dashboard upon successful authentication, instead of the landing page. This ensures users are directed to the application's core functionality after logging in.
- Removed the user profile button from the dashboard and added it to the menu bar.
- Implemented a landing page with the specified features and styling.
- Apply color adjustments to transaction values, icons, and dashboard cards.
- Fix the visibility of the "Nova Receita" and "Nova Despesa" buttons.
- Address the issue of the site adopting a black color scheme.
- Add an indicator to the menu toggle button.
Replaced the existing sidebar with a new implementation for improved mobile compatibility and functionality. Also, addressed the webhook issue and provided guidance on manual verification.
- Moved the user profile button back to the dashboard, above the month filter.
- Configured the "Fale Conosco" form to send data to the specified webhook and display a success message to the user.
- Fixed build error in `src/components/help/ContactForm.tsx` by correcting the import of `enviarFaleConoscoParaWebhook`.
The user profile dropdown was not working correctly, and the icon was cut off. This commit fixes the dropdown functionality and ensures the icon is fully visible.
- Removed the blue hover effect from the menu items.
- Added user profile with email and logout button.
- Installed necessary dependencies.
- Created button component.
- Replace the blue rectangle with the logo.
- Extend the sidebar menu.
- Change the login/password screen background.
- Add and integrate the BackgroundBoxesDemo component.
Integrate the provided sidebar component, ensuring it functions correctly on both desktop and mobile devices with automatic collapsing and expanding functionality.
The AI corrected the `Assinatura` page to pass the user's email and ID in the request body when calling the `mercado-pago-subscribe` Supabase function, resolving the "E-mail ou ID do usuário não fornecido" error.
The AI addressed the app crashing after login and investigated the subscription page issue, focusing on resolving the problem to display the purchase page, without providing logs.
The AI fixed the dashboard not displaying transaction values by reviewing the data fetching and display logic. It also addressed the "Assinar Agora" button not working by checking the Mercado Pago integration and subscription page.
- Fixed dashboard data not loading from the database.
- Fixed onboarding tour looping and showing repeated banners.
- Fixed "Assinar Agora" button not redirecting to payment page.
The AI fixed a runtime error related to `removeHighlightStyle` in `src/components/onboarding/OnboardingTour.tsx` and addressed the issue of the app page not appearing.
The AI fixed the onboarding tour logic to ensure it appears on login if the user has no registered groups, addressing the issue of the tour not appearing despite the conditions being met.
The AI addressed the 404 error on the subscription page and investigated the onboarding tour not starting after login when no groups are registered. It also reviewed the code for potential errors in the tour logic.
The onboarding tour was not starting correctly after login. This commit reviews the logic to ensure the tour starts when the user logs in and has no registered groups. Also, it moves the "Assinatura" menu item to the end of the sidebar, after "Calendário".
Restore the user identification section in the header. Improve the category chart by removing the value from the center and improving the tooltip display.
- Added an arrow connecting the text in the banner to the button in the onboarding tour.
- Adjusted the "Grupos" button style to match the original design, ensuring a white background and black text.
Fixes the onboarding tour looping issue and adjusts the button style for better visibility. The tour now correctly opens only once per session until the required conditions are met (connected instance and active group).
Implement an onboarding tour that guides users through connecting WhatsApp and creating a group. The tour should only appear until the user has created at least one instance and one group.
This commit executes the provided SQL script to create the necessary tables (`faqs`, `faq_feedback`, `contatos`) and associated policies for the help system, as reviewed by the user. It also creates a storage bucket for contact form attachments.
Implement a help icon with a "Fale com a gente" button, linking to an email form. Add admin functionality to create FAQs with text and image support, including a feedback mechanism.
Unifies instance verification logic using `useExistingInstanceCheck` across components, corrects the Supabase query, and adds re-verification after instance creation to resolve inconsistencies in WhatsApp instance detection and group creation.
The AI identified that the WhatsApp connection page was not updating correctly, and the previous fixes were not working. It suggests a new approach, analyzing the old and current logic, and checking for other potential issues.
Analyze and fix the logic for WhatsApp instance and group creation, ensuring correct instance detection based on user email and status. Also, check for any exposed API keys or sensitive information.
The previous changes did not fully resolve the issue. This commit ensures the correct instance detection logic is implemented, based on the user's email and the instance status in the database. This affects the creation of new instances and group creation.
Ensure instance creation logic checks 'instancia_zap' and 'status_instancia' in the 'usuarios' table. Allow group creation only when 'status_instancia' is 'conectado'.
Refactors CreateGroupForm.tsx into smaller, more manageable components and hooks to improve code organization and readability. This includes creating new files for specific functionalities and logic, enhancing maintainability.
This commit refactors the CreateInstanceForm.tsx component into smaller, more manageable files to improve code organization and maintainability. This includes splitting the form into logical sub-components and potentially moving related hooks or utilities into separate files. Unused imports and files are also removed.
The previous fix for instance detection was not fully effective. This commit further refines the logic in `src/components/whatsapp/CreateInstanceForm.tsx` and `src/components/whatsappGroups/CreateGroupForm.tsx` to ensure that the app correctly identifies existing WhatsApp instances and prevents the creation of duplicate instances or groups.
The logic for enabling WhatsApp group creation was not correctly recognizing when a WhatsApp instance was created, allowing users to attempt to create multiple instances. This commit addresses the issue.
The user reported that the app allows navigation without completing the profile (Name, WhatsApp) after Google login, and the N8N webhook is not triggered. This commit addresses these issues by ensuring the `/complete-profile` page is shown until the required data is provided, and the `sendNewUserWebhook` is called after successful profile completion.
The Google OAuth redirect was failing in production due to `window.location.origin` resolving to `localhost:3000`. This commit fixes the redirect logic in `src/components/auth/SocialLoginButtons.tsx` and updates the `public.handle_new_user()` function via a SQL migration (`supabase/migrations/20250621141237-fix-google-user-data.sql`) to capture the user's name from Google metadata.
