Core multitenants#11
Merged
Merged
Conversation
Feature/get started
Feature/get started
Agregar definición de tipos para Mercado Pago y actualizar .gitignore…
Agregar configuración de ESBuild y asegurar instalación de dependenci…
Optimizar comandos de instalación en amplify.yml para la función crea…
Actualizar ruta de instalación de dependencias en amplify.yml para la…
Agregar comando para regresar al directorio raíz antes de la instalac…
Actualizar ruta de retorno en amplify.yml para mejorar la instalación…
Agregar configuración de externals para mercadopago en next.config.js
Eliminar configuración de externals para mercadopago en next.config.j…
Agregar configuración de externals para mercadopago en next.config.js
Eliminar comandos innecesarios en amplify.yml y simplificar configura…
Eliminar archivos de configuración de mercadopago en esbuild y tipos …
Agregar definición de tipos para Mercado Pago y reordenar importacion…
Eliminar configuración de externals para mercadopago en next.config.j…
Eliminar archivos y tipos de configuración de Mercado Pago en el proy…
Feature/get started
This commit introduces two new Lambda functions, `getStoreData` and `getStoreProducts`, along with their respective REST APIs. These functions allow fetching store data and products by store ID. Additionally, the data schema is updated to include secondary indexes and authorization rules for these functions. The APIs are configured with CORS support and integrated into the backend stack.
…ions This commit introduces a comprehensive collection management feature, including: - New collection model in Amplify schema - Collection CRUD operations with React Query - Collection pages for listing, creating, and editing collections - Integration with S3 for image storage - Product selection and management within collections - UI components for collection management The feature supports full lifecycle management of product collections, including image handling, product association, and SEO optimization.
…oudFront integration - Added collection form with CRUD operations, product selection, and unsaved changes alert - Implemented collections table with filtering, sorting, and CloudFront URLs for images - Integrated CloudFront for image URLs in product uploads and collections - Enhanced UI components for collection management with loading states and error handling
This commit introduces a new function `getStoreCollections` to retrieve store collections based on query parameters. It includes the function definition, handler implementation, and integration with the existing backend API. The function supports fetching collections by ID, slug, or all collections for a given store. The API is exposed via a new REST endpoint `/get-store-collections` with appropriate IAM policies and CORS configuration.
Update issue templates
Bumps [next](https://github.com/vercel/next.js) from 14.2.10 to 14.2.28. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.10...v14.2.28) --- updated-dependencies: - dependency-name: next dependency-version: 14.2.28 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Bump next from 14.2.10 to 14.2.28
Bumps [cross-spawn](https://github.com/moxystudio/node-cross-spawn) from 7.0.3 to 7.0.6. - [Changelog](https://github.com/moxystudio/node-cross-spawn/blob/master/CHANGELOG.md) - [Commits](moxystudio/node-cross-spawn@v7.0.3...v7.0.6) --- updated-dependencies: - dependency-name: cross-spawn dependency-version: 7.0.6 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [nanoid](https://github.com/ai/nanoid) from 3.3.7 to 3.3.11. - [Release notes](https://github.com/ai/nanoid/releases) - [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md) - [Commits](ai/nanoid@3.3.7...3.3.11) --- updated-dependencies: - dependency-name: nanoid dependency-version: 3.3.11 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [@babel/runtime](https://github.com/babel/babel/tree/HEAD/packages/babel-runtime) from 7.25.9 to 7.27.0. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v7.27.0/packages/babel-runtime) --- updated-dependencies: - dependency-name: "@babel/runtime" dependency-version: 7.27.0 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [esbuild](https://github.com/evanw/esbuild) and [tsx](https://github.com/privatenumber/tsx). These dependencies needed to be updated together. Updates `esbuild` from 0.23.1 to 0.25.2 - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md) - [Commits](evanw/esbuild@v0.23.1...v0.25.2) Updates `tsx` from 4.19.2 to 4.19.3 - [Release notes](https://github.com/privatenumber/tsx/releases) - [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs) - [Commits](privatenumber/tsx@v4.19.2...v4.19.3) --- updated-dependencies: - dependency-name: esbuild dependency-version: 0.25.2 dependency-type: direct:development - dependency-name: tsx dependency-version: 4.19.3 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
…functions/webHookPlan/src/axios-1.8.2 Bump axios from 1.7.9 to 1.8.2 in /amplify/functions/webHookPlan/src
…3.11 Bump nanoid from 3.3.7 to 3.3.11
Bumps [aws-cdk](https://github.com/aws/aws-cdk-cli/tree/HEAD/packages/aws-cdk) from 2.176.0 to 2.1010.0. - [Release notes](https://github.com/aws/aws-cdk-cli/releases) - [Commits](https://github.com/aws/aws-cdk-cli/commits/aws-cdk@v2.1010.0/packages/aws-cdk) --- updated-dependencies: - dependency-name: aws-cdk dependency-version: 2.1010.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
…wn-7.0.6 Bump cross-spawn from 7.0.3 to 7.0.6
….1010.0 Bump aws-cdk from 2.176.0 to 2.1010.0
Updated various configuration files and dependencies to improve project maintainability. This includes adding new dependencies, updating existing ones, and removing unused imports. Also, adjusted Next.js dev script to use Turbopack for faster development builds.
This change specifies the package manager to be used for the project, ensuring consistency in dependency management across different environments.
The packageManager field was removed from package.json to avoid conflicts with Node.js version management. Additionally, a .nvmrc file was added to specify the Node.js version for the project, ensuring consistent environment setup.
The change was made to standardize the package manager used in the pre-commit hook, ensuring consistency across the development environment. This avoids potential issues caused by differing package managers.
The pre-commit hook was updated to use `npx lint-staged` instead of `npm lint-staged` to ensure the correct execution of lint-staged scripts.
Update the Prettier workflow to exclude the `.github/` directory from being staged for formatting changes. This prevents unnecessary commits for changes in CI configuration files.
The next.config.js file has been replaced with next.config.ts to leverage TypeScript's type safety. This change ensures better maintainability and reduces the risk of runtime errors by providing static type checking.
Update environment variable imports to use the $amplify alias for consistency and remove unnecessary debug logs in the planScheduler handler to improve code cleanliness and reduce noise in the logs.
The console.log statement was removed as it was unnecessary and added no value to the function's logic. This improves code cleanliness and reduces unnecessary output during execution.
Clean up the handler.ts file by removing redundant console.log statements to improve code readability and reduce clutter. This change does not affect the functionality of the code.
The console.log statement for the received signature was removed as it was not required for the functionality and added unnecessary logging clutter.
This commit introduces Jest configuration, setup files, and mocks for testing. It also includes a comprehensive unit test suite for the StoreSelector component, ensuring its functionality is thoroughly validated. Additionally, the useUserStores hook is refactored to support Suspense for better data fetching in React.
…assword hooks This commit introduces comprehensive unit tests for the StoreSelector component and the signUp, SignIn, and useResetPassword hooks. The tests cover various scenarios, including successful operations, error handling, and edge cases, ensuring robust functionality and reliability.
The commit adds an import statement for `amplify_outputs.json` in the `SignIn.test.ts` file to ensure the test suite has access to the necessary Amplify configuration during testing.
This change adds the `rootDir` configuration to the Jest configuration file, ensuring that Jest correctly resolves the root directory for test execution. This is necessary to avoid potential issues with module resolution in the project structure.
…e jest config The commit removes redundant mocks for `amplify_outputs.json` across multiple test files and updates the Jest configuration to include a mock file for `amplify_outputs.json` in the `__mocks__` directory. This improves maintainability by centralizing the mock configuration and reducing duplication.
This commit introduces a mock for the `amplify_outputs.json` file in the unit tests for the `useAuth` and `signUp` hooks to ensure consistent test behavior. Additionally, it suppresses console warnings globally in the Jest setup to reduce noise during test execution.
The Amplify.configure calls were removed from the authentication hooks and their corresponding test files to simplify the codebase and eliminate redundant configuration. The mocks for amplify_outputs.json were also removed as they are no longer needed. This change improves maintainability and reduces unnecessary dependencies.
The file was deleted as it is no longer needed in the project structure. This cleanup helps maintain a cleaner and more organized codebase.
To prevent tracking of amplify's node_modules directory, which is unnecessary and can be regenerated, it has been added to the .gitignore file.
The file was deleted as it is no longer needed in the project, likely due to changes in the Amplify configuration or environment setup.
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.
No description provided.