release-20251211 #212
Merged
release-20251211 #212
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tDossiersByCampaign response
UN-2132-add-autoapprove-check
…with new components and layout
…s message for clarity
…te details section
…w components and layout
…community costs and human resources management
…en usage and linked agreements
…venue Overview and Cost & Resource Details sections
…ching for agreements and costs
…rmik for better state management
…rmik for better state management
…handling and API integration
…card side summary finance card
feat(RevenueOverviewSection): add success and error messages on data …
… structure and improve data flow
…ing in form values
…nd enhance validation
fix(CostAndResourceDetailsSection): correct prospect link URL format
feat(HumanResources): add confirmation modal for deleting cost items
fix(RevenueOverviewSection): move save button inside card for better …
…nd navigation refactor(QuoteBanner): simplify status message component fix(HumanResources): align save button to the right refactor(RevenueOverviewSection): update import paths for consistency refactor(QuoteHistorySection): adjust import paths for section component refactor(CostAndResourceDetailsSection): reorganize imports for clarity
feat(HumanResources): add subtotals and total calculation for HR costs
…cost, and gross margin
feat(SummaryFinanceCard): adjust title size for total revenue, total …
…al revenue and total cost
feat(SummaryFinanceCard): replace spans with Title components for tot…
Update remove hr row behaviour
…to 0.00 for financial displays
…m value for assignee, days, and role
fix(HumanResources): remove ErrorMessage component from FormContent
feat(RevenueOverviewSection, SummaryFinanceCard): set default values …
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces several improvements and refactors across multiple pages, focusing on UI consistency, maintainability, and new feature support. The most significant changes include standardizing button usage across pages, adding support for an AI-powered bug approval feature in campaign forms, and introducing a new context for managing quote form navigation.
UI Consistency and Refactoring
HeaderButtoncomponents with direct usage of theButtoncomponent from@appquality/appquality-design-systemin several pages (BugsList,Prospect,Agreements List), ensuring consistent props and appearance. [1] [2] [3] [4] [5] [6]2.0.10inpackage.jsonfor access to the latest features and fixes.Campaign Form Feature Enhancements
autoApprove(AI-powered bug approval) field to the campaign form, including its state management, validation, and submission logic. Introduced a newAutoApprovefield component and integrated it into the form UI. [1] [2] [3] [4] [5] [6]Quote Page Improvements
QuoteFormContextto manage navigation between sections in the quote form, improving user experience for multi-section forms.General Code Quality and Type Safety
onChangeevent handlers to use explicitanytyping where necessary for compatibility with Formik and design system components. [1] [2] [3] [4] [5] [6] [7] [8]These changes collectively improve the maintainability, consistency, and feature set of the backoffice application.