fix: fetch user data with uuid /me route

[luisgustavoo]

When calling the /me route to fetch data from the logged in user, it is returning a 500 error, as the user has a uuid and not an int id.

[rodrigorahman]

@luisgustavoo Escrevi 2 testes para validar a implementação do me para aquando for int ou uuid.

O seu código não passa quando estamos trabalhando com uuid.

Atualiza sua branch para pegar os testes e coloca na sua alteração a verificação do tipo do idType:

    final idUser = switch(_config.idType) {
      IdTypeEnum.int => int.parse(id),
      IdTypeEnum.uuid => id,
    };

[luisgustavoo]

Blz, vou atualizar aqui! Valeu

[gitguardian]

⚠️ GitGuardian has uncovered 7 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
4262883	Triggered	Generic High Entropy Secret	42dd5bb	test/server/server_config/config.yaml	View secret
4262883	Triggered	Generic High Entropy Secret	75b7746	test/server/mock/auth_custom_fields_config.json	View secret
4262883	Triggered	Generic High Entropy Secret	75b7746	test/server/server_config/config.yaml	View secret
4262883	Triggered	Generic High Entropy Secret	75b7746	test/server/server_config/config_bk.yaml	View secret
4262883	Triggered	Generic High Entropy Secret	75b7746	test/server/server_config/config.yaml	View secret
4262883	Triggered	Generic High Entropy Secret	75b7746	test/server/mock/auth_default_config.json	View secret
4262883	Triggered	Generic High Entropy Secret	75b7746	test/server/mock/auth_default_id_int_config.json	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

• 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.}