Ft recollect single trainee details

[tysepa]

What does this PR do?

this PR show all information and the details of the trainee and Application cycles

Description of Task to be completed?

Trainee_id is required to view all the trainee details and information
All trainees are in the table you can access it and check their cycle
Also Has dark mode and right mode

How should this be manually tested?

Clone the repo

checkout to branch ft-recollect-single-trainee-details

Install all the required packages by running npm install

Start the app by running npm run dev

All mode

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
atlp-devpulse-fn	❌ Failed (Inspect)			Sep 13, 2024 6:59am

[netlify]

❌ Deploy Preview for ubiquitous-heliotrope-e71dc6 failed.

Name	Link
🔨 Latest commit	5f3bba4
🔍 Latest deploy log	https://app.netlify.com/sites/ubiquitous-heliotrope-e71dc6/deploys/638f02f339924a00081c29a7

[netlify]

❌ Deploy Preview for moonlit-biscotti-cd8e0d failed.

Name	Link
🔨 Latest commit	5f3bba4
🔍 Latest deploy log	https://app.netlify.com/sites/moonlit-biscotti-cd8e0d/deploys/638f02f31b2c3c00082def3f

[netlify]

❌ Deploy Preview for iridescent-llama-25540d failed.

Name	Link
🔨 Latest commit	5f3bba4
🔍 Latest deploy log	https://app.netlify.com/sites/iridescent-llama-25540d/deploys/638f02f3a7a82f0007dae52d

[netlify]

❌ Deploy Preview for incomparable-froyo-881dcf failed.

Name	Link
🔨 Latest commit	5f3bba4
🔍 Latest deploy log	https://app.netlify.com/sites/incomparable-froyo-881dcf/deploys/638f02f38b1d570008ec74b7

[netlify]

❌ Deploy Preview for sparkly-twilight-057a8e failed.

Name	Link
🔨 Latest commit	5f3bba4
🔍 Latest deploy log	https://app.netlify.com/sites/sparkly-twilight-057a8e/deploys/638f02f3a7a82f0007dae532

[Gedeonir]

Try to make applicant information to render after fetching data as you did on applicant info
and remove white space at the bottom in dark mode

[Gedeonir]

Try to make applicant information to render after fetching data as you did on applicant info
and remove white space at the bottom in dark mode

[tysepa]

Try to make applicant information to render after fetching data as you did on applicant info and remove white space at the bottom in dark mode

the reason's why that page can be open because it gets the Id from that table of trainees and it uses that URL on the link

[Gedeonir]

But we can have something which is being displayed while querry is loading instead of undefined

[netlify]

✅ Deploy Preview for fluffy-bubblegum-5cc8d0 ready!

Name	Link
🔨 Latest commit	5f3bba4
🔍 Latest deploy log	https://app.netlify.com/sites/fluffy-bubblegum-5cc8d0/deploys/638f02f39b84cc0009323c4e
😎 Deploy Preview	https://deploy-preview-40--fluffy-bubblegum-5cc8d0.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

❌ Deploy Preview for bejewelled-treacle-52af2a failed.

Name	Link
🔨 Latest commit	5f3bba4
🔍 Latest deploy log	https://app.netlify.com/sites/bejewelled-treacle-52af2a/deploys/638f02f39bef100008d6042d

[netlify]

❌ Deploy Preview for super-rugelach-3905b4 failed.

Name	Link
🔨 Latest commit	5f3bba4
🔍 Latest deploy log	https://app.netlify.com/sites/super-rugelach-3905b4/deploys/638f02f35a3b140009969590

[PrinceNiyonshuti]

Looks good to me

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
7140290	Triggered	Generic High Entropy Secret	b152475	src/components/tinymce/Tinymce.tsx	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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.}

[codeclimate]

Code Climate has analyzed commit f22c19f and detected 23 issues on this pull request.

Here's the issue category breakdown:

Category	Count
Duplication	18
Bug Risk	1
Clarity	4

View more on Code Climate.