Skip to content

Conversation

@SaboniAmine
Copy link
Member

Description

Various code factorization / error management / magic values cleaning.

Motivation and Context

Standardisation of the codebase

How Has This Been Tested?

Deployed on test env

Screenshots (if appropriate):

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING.md document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@SaboniAmine SaboniAmine requested a review from a team as a code owner November 4, 2025 11:34
SaboniAmine and others added 8 commits November 4, 2025 12:35
feat(front): add modal to call deletion endpoints for projects
standardise api call with fetchApi instead of fetch + injected url,
refactor Modal usage with custom hook
feat(front): add modal to call deletion endpoints for projects
feat(front): add modal to call deletion endpoints for projects
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants