-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chore/mobile/refactor #273
Conversation
Tests: 16 passed, 16 total
This commit adds an authentication check before making the API call to fetch user bookings. If the authentication token is not found, an error response is returned with the appropriate error code and message.
Tests: 13 passed, 13 total Snapshots: 0 total Time: 4.245 s
…2024/occupi into chore/mobile/refactor
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
13149987 | Triggered | Generic Password | 7ba4f7f | frontend/occupi-mobile4/services/authservices.ts | View secret |
13149987 | Triggered | Generic Password | 5c4f173 | frontend/occupi-mobile4/services/authservices.ts | View secret |
13149987 | Triggered | Generic Password | 81dfca9 | frontend/occupi-mobile4/services/authservices.ts | View secret |
13149987 | Triggered | Generic Password | 908a89c | frontend/occupi-mobile4/services/authservices.ts | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Description
This pr introduces a refactored mobile with a file structure that makes the system more readable. It includes an update to storage of the different data such as user data, user settings, as well as the current state of the app for state management. (this will allow rollbacking to a stable state should there be any issues. This pr also introduces the setting of profile details upon registering a new account, however there is a small issue ther that will be addressed in due time.
It also includes multiple fixes including:
Fixes #272, #241
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist: