Skip to content
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

Merged
merged 105 commits into from
Aug 6, 2024
Merged

Chore/mobile/refactor #273

merged 105 commits into from
Aug 6, 2024

Conversation

KamogeloMoeketse
Copy link
Contributor

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:

  • updating of profile details
  • updating theme and accent colours
  • added ThemeContext

Fixes #272, #241

Type of change

Please delete options that are not relevant.

  • 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 not work as expected)
  • This change requires a documentation update

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

  • Test A
  • Test B

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

KamogeloMoeketse and others added 30 commits July 23, 2024 22:10
u21631532 and others added 25 commits August 2, 2024 11:40
      √ should return token when it exists (1 ms)
      √ should return undefined when token does not exist (1 ms)
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
Copy link

gitguardian bot commented Aug 6, 2024

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
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
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. 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


🦉 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.

@KamogeloMoeketse KamogeloMoeketse merged commit 84c76f6 into develop Aug 6, 2024
1 of 9 checks passed
waveyboym pushed a commit that referenced this pull request Aug 9, 2024
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.

[TASK]Fix Appearance Settings
3 participants