Conversation
- Introduced a new script `remove-localization.ts` that processes TypeScript files to replace localization function calls with hardcoded strings. - Added a new npm script command `remove-localization` in `package.json` to trigger the localization removal process. - The script builds a complete translation map and cleans up related imports and declarations, ensuring a smooth transition away from localization handling.
- Added a new script `remove-localization.js` to replace localization function calls with hardcoded strings in TypeScript files. - Enhanced the existing `remove-localization.ts` script with improved translation map building and file processing logic. - Introduced a TypeScript configuration file `tsconfig.script.json` for the new script. - The script logs progress and warnings, ensuring a smooth transition away from localization handling.
…zation-action.ts - Removed duplicate import of addFrameworksSchema for clarity. - Adjusted formatting for consistency in the visibility condition. - Ensured no newline at the end of the file for adherence to coding standards.
… strings in error pages and controls - Eliminated localization imports and functions from NotFound and Unauthorized pages, replacing them with hardcoded strings for titles and descriptions. - Updated the Controls page to use a hardcoded title instead of a localized one. - Adjusted PoliciesTable component to display hardcoded column titles instead of localized values.
- Eliminated the use of localization functions and replaced them with hardcoded strings for column titles and the card title in the RequirementsTable component. - This change simplifies the component by removing unnecessary dependencies on localization.
- Eliminated the use of localization functions and imports across multiple components, replacing them with hardcoded strings for titles and column headers. - This change simplifies the components by reducing dependencies on localization, enhancing readability and maintainability.
- Removed localization imports and functions from multiple components, replacing them with hardcoded strings for titles and descriptions. - This change simplifies the components by reducing dependencies on localization, improving readability and maintainability.
…onents - Removed localization imports and functions from multiple components, substituting them with hardcoded strings for titles, labels, and descriptions. - This change enhances component readability and maintainability by reducing dependencies on localization.
…omponents - Removed localization imports and functions from various components, substituting them with hardcoded strings for titles, labels, and descriptions. - This change improves component readability and maintainability by reducing dependencies on localization.
…omponents - Removed localization imports and functions from various components, substituting them with hardcoded strings for titles, labels, and descriptions. - This change improves component readability and maintainability by reducing dependencies on localization.
…rings - Eliminated localization dependencies in the PoliciesTable component by replacing localized placeholders with hardcoded strings. - Updated the useApiKeys hook to remove localization references, enhancing component simplicity and maintainability.
…uirements components - Eliminated localization dependencies by replacing localized placeholders with hardcoded strings in the RequirementsTable and FrameworkRequirements components. - This change enhances component simplicity and maintainability by reducing reliance on localization.
- Eliminated localization dependencies by removing the localization variable from the RequirementControlsTable component. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Replaced localized status strings with hardcoded values in the FrameworkCard component. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Replaced localized strings with hardcoded values for labels, placeholders, and descriptions in the InviteMembersModal component. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Replaced localized strings with hardcoded values for labels, placeholders, and descriptions in the MemberRow component. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Eliminated localization dependencies by removing the localization variable from MultiRoleCombobox, MultiRoleComboboxContent, and MultiRoleComboboxTrigger components. - This change simplifies the components and enhances maintainability by reducing reliance on localization.
… and PolicyOverviewSheet components - Eliminated localization dependencies by replacing localized strings with hardcoded values in the PolicyStatusChart, PolicyOverview, and PolicyOverviewSheet components. - This change simplifies the components and enhances maintainability by reducing reliance on localization.
…ialog components - Replaced localized strings with hardcoded values for descriptions, questions, and answers in the RiskRegisterPage component. - Updated the placeholder in the CreateApiKeyDialog component to a hardcoded string. - This change simplifies the components and enhances maintainability by reducing reliance on localization.
…mponents - Replaced localized strings with hardcoded values for labels, placeholders, and descriptions in the CreateVendorForm and CreateRisk components. - This change simplifies the components and enhances maintainability by reducing reliance on localization.
- Replaced localized strings with hardcoded values for labels and placeholders in the PolicyOverview component. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Replaced localized strings with hardcoded values for error messages, upload status, and drop instructions in the FileUploader component. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Replaced localized strings with hardcoded values for the vendor management description and FAQ questions and answers in the backup-overview layout component. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Replaced localized strings with hardcoded values for preview messages, file names, and alert dialog content in the FileCard component. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Replaced localized strings with hardcoded values for FAQ questions and answers in the CloudTests component. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Replaced localized strings with hardcoded values for FAQ questions and answers in the vendor overview page component. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Deleted the LocaleSwitch component to eliminate localization dependencies. - This change simplifies the codebase and enhances maintainability by reducing reliance on localization.
- Replaced localized string for the no notifications message with a hardcoded value. - This change simplifies the component and enhances maintainability by reducing reliance on localization.
- Deleted the NotificationCenter component to simplify the codebase and enhance maintainability. - Removed unused imports and references in the Header component, streamlining its functionality.
- Replaced localized strings with hardcoded values for labels and placeholders in the CreateVendorTaskForm and UpdatePolicyForm components. - This change simplifies the components and enhances maintainability by reducing reliance on localization.
- Introduced a new migration to update foreign key constraints for multiple models (Attachment, Context, Onboarding, Task, VendorContact) to include ON DELETE CASCADE behavior. - Updated the Prisma schema for these models to reflect the new cascading delete relationships, enhancing data integrity and simplifying deletion processes.
- Removed localization parameters from the MemberRow component, simplifying the code and enhancing maintainability. - Adjusted the useParams hook to eliminate locale handling and updated the profile link accordingly. - Integrated AlertDialog components for improved user interaction.
…letion-via-cascade [dev] [claudfuen] claudio/comp-182-enable-org-deletion-via-cascade
…profile-broken-link [dev] [claudfuen] claudio/comp-183-fix-employee-profile-broken-link
- Removed unused loading state and helper function for display names. - Enhanced organization name display logic to handle duplicates more effectively. - Streamlined organization selection handling and dialog state management for improved clarity and maintainability.
…emove-biome-from-codebase
- Added new dependencies: languine, next-international, and next-intl in bun.lock. - Updated versions for several Babel packages and other dependencies in both bun.lock and yarn.lock. - Improved dependency management by ensuring compatibility and resolving version discrepancies.
- Modified the branch naming pattern to allow hyphens and require a more general format. - Updated the error message to reflect the new naming convention: category/branch-name (e.g. feature/add-button).
- Changed the reference for setting the pending organization ID from `args.organizationId` to `args.input.organizationId` to align with the updated input structure.
…h-double-selected-orgs [dev] [claudfuen] claudio/comp-184-fix-issue-with-double-selected-orgs
Remove Biome configs and switch to Prettier
[dev] [claudfuen] claudio/fix-main
Contributor
|
🎉 This PR is included in version 1.34.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.