device-management-toolkit / device-management-toolkit/sample-web-ui
Expired domain cert toast shows wrong count
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 19
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 49
Description
Description
The Domains table correctly flags a profile's certificate as "Expired", but the toast notification shows "0 DOMAIN CERT(S) ARE EXPIRED" instead of the correct count.
Steps to Reproduce
- Go to the Domains page with a domain profile whose certificate is expired.
- Note the table shows "Expired" for that profile.
- Check the toast notification at the bottom of the page.
Expected Behavior
Toast should show the correct expired count (e.g. "1 domain cert(s) are expired").
Actual Behavior
Toast shows "0 domain cert(s) are expired".
Environment
- Console v1.41.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start on the Domains page and compare how the table determines an expired certificate with the value used for the toast notification count. Reproduce the issue with an expired domain profile, then verify that the toast count matches the number of profiles marked "Expired".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100