SUM-260: adding a tooltip

[jenbreese]

NOT READY FOR REVIEW

• This really isn't ready for code review. @pookmish can you give me some feedback on how to improve it? There is a React error I haven't figure out yet too.

Summary

• TL;DR - what's this PR for?

Review By (Date)

• When does this need to be reviewed by?

Criticality

• How critical is this PR on a 1-10 scale? Also see Severity Assessment.
• E.g., it affects one site, or every site and product?

Urgency

• How urgent is this? (Normal, High)

Review Tasks

Setup tasks and/or behavior to test

1. Check out this branch
2. Rebuild Cache and import config drush cr ; drush ci
3. Navigate to...
4. Verify...

Site Configuration Sync

• Is there a config:export in this PR that changes the config sync directory?

Front End Validation

• Design is approved by @ user?
• HTML validation: Is the markup using the appropriate semantic tags and passes validation? Or, QA request ticket created?
• Cross-browser testing: Has been performed? Or, QA request ticket created?
• Automated accessibility: Scans performed? Or, QA request ticket created?
• Manual accessibility: Manually tested? Or, QA request ticket created?

Backend / Functional Validation

Code

• Are the naming conventions following our standards?
• Does the code have sufficient inline comments?
• Is there anything in this code that would be hidden or hard to discover through the UI?
• Are there any code smells?
• Are tests provided? eg (unit, behat, or codeception)

Code security

• Are all forms properly sanitized?
• Any obvious security flaws or new areas for attack?

General

• Is there anything included in this PR that is not related to the problem it is trying to solve?
• Is the approach to the problem appropriate?

Affected Projects or Products

• Does this PR impact any particular projects, products, or modules?

Associated Issues and/or People

- SUM-260

Resources

• AMP Tool
• Accessibility Manual Test Script
• HTML Validator
• Browserstack and link to Browserstack Credentials

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
summer	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 19, 2024 4:49am

[pookmish]

The way you are going about this is much more complex than needs to be. take a look at react-toastify to see if it will do the work you are looking for.

Also, it's highly discouraged to ever put a component inside a function. Not to mention you can't have a hook like useState inside a function. I strongly recommend going through some react trainings for hooks and components. Some possible resources:

• https://legacy.reactjs.org/docs/hooks-state.html
• https://www.youtube.com/watch?v=O6P86uwfdR0&list=PLZlA0Gpn_vH8EtggFGERCwMY5u5hOjf-h

[jenbreese]

I'm closing this because I'm redoing it.