betagouv / preuve-covoiturage

Registre de preuve de covoiturage
https://app.covoiturage.beta.gouv.fr
Apache License 2.0
33 stars 12 forks source link

bugfix: listing des campagnes pour les ops #2464

Closed jonathanfallon closed 5 months ago

jonathanfallon commented 5 months ago

fix de l'affichage des campagnes liés au passage à l'UUID

Summary by CodeRabbit

coderabbitai[bot] commented 5 months ago

Walkthrough

The recent updates focus on refining the project's configuration and codebase, particularly around the API and shared interfaces. Key adjustments include streamlining PM2 configurations, enhancing the S3 storage debugging capability, and shifting the operator identification method from SIRET numbers to UUIDs. These changes signify a move towards more efficient code management and a stronger emphasis on unique identifiers for operator management, improving both the development workflow and the system's reliability.

Changes

Files Summary
.vscode/settings.json Commented out "api/**/dist": true.
api/pm2-api.json, api/pm2-worker.json Updated script paths and simplified watch configurations.
.../storage/S3StorageProvider.ts Reordered imports, removed duplicates, added debug log in list method.
.../providers/OperatorPgRepositoryProvider.integration.spec.ts Added uuid field to a test object.
.../services/policy/actions/FindAction.ts, .../ListAction.ts Shifted from SIRET to UUID for operator identification, updated permission error messages.
shared/operator/common/interfaces/OperatorDbInterface.ts, .../OperatorInterface.ts Made uuid a required field in OperatorDbInterface, added uuid to OperatorInterface.

"In the realm of code, where logic does play,
A rabbit hopped in, making changes today.
🐰 With a flick and a hop, configurations refine,
UUIDs in the spotlight, uniquely define.
Debug logs for clarity, paths now succinct,
Our rabbit's swift work, in code does imprint.
Celebrate we shall, for improvements are here,
In the digital burrow, progress is near."


Recent Review Status **Configuration used: CodeRabbit UI**
Commits Files that changed from the base of the PR and between 623ae2e6b43fbfde0f9f62eff7c024e93e92157c and 07fde01819c27317c131b5853337c1ec7e9e396e.
Files selected for processing (9) * .vscode/settings.json (1 hunks) * api/pm2-api.json (1 hunks) * api/pm2-worker.json (1 hunks) * api/src/pdc/providers/storage/S3StorageProvider.ts (2 hunks) * api/src/pdc/services/operator/providers/OperatorPgRepositoryProvider.integration.spec.ts (1 hunks) * api/src/pdc/services/policy/actions/FindAction.ts (1 hunks) * api/src/pdc/services/policy/actions/ListAction.ts (1 hunks) * shared/operator/common/interfaces/OperatorDbInterface.ts (1 hunks) * shared/operator/common/interfaces/OperatorInterface.ts (1 hunks)
Additional comments not posted (10)
shared/operator/common/interfaces/OperatorDbInterface.ts (1)
`5-5`: Making `uuid` a required property aligns with the shift towards using UUIDs for operator identification. Ensure all usages of `OperatorDbInterface` across the codebase are updated to provide a `uuid`.
api/pm2-api.json (1)
`3-3`: The updates to the script path and watch configuration are appropriate and should help streamline the development and deployment process. Also applies to: 7-7
api/pm2-worker.json (1)
`3-3`: The updates to the script path and watch configuration are consistent with best practices and should enhance the development and deployment process. Also applies to: 7-7
shared/operator/common/interfaces/OperatorInterface.ts (1)
`10-10`: The addition of the `uuid` field is crucial for the shift towards using UUIDs for operator identification. Ensure consistency across all related interfaces and implementations.
.vscode/settings.json (1)
`43-43`: Commenting out `"api/**/dist": true` may adjust the development environment settings. Consider documenting the reason for this change to provide context for future developers.
api/src/pdc/services/policy/actions/FindAction.ts (1)
`61-62`: Updating the permission check logic to use the operator's UUID instead of the SIRET number is a critical change that aligns with the shift towards UUIDs. Ensure thorough testing of the updated logic.
api/src/pdc/services/policy/actions/ListAction.ts (1)
`71-71`: The update to use `operator.uuid` in the `withOperator` method aligns with the shift towards UUIDs. Ensure that all related filtering and permission checks across the system are updated accordingly.
api/src/pdc/services/operator/providers/OperatorPgRepositoryProvider.integration.spec.ts (1)
`51-51`: The addition of the `uuid` field in the test object is necessary for consistency with the updated operator identification strategy. Ensure all relevant tests are updated accordingly.
api/src/pdc/providers/storage/S3StorageProvider.ts (2)
`58-58`: Consider refining the logging strategy to ensure it's appropriate for all environments. Excessive logging can clutter log files and incur costs in production. Perhaps conditionally enable detailed logging based on the environment or a configuration setting. --- `9-18`: > :memo: **NOTE** > This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [1-11] Reordering imports and removing duplicates are good practices for improving code quality and maintainability. Keep up the good work!
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
---
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.