Audit follow-up: UVE quick-edit panel spins forever when content-type fetch fails
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Parent epic: #36004
Finding
withContentTypeCache.ts reportedly handles content-type fetch failure with catchError -> EMPTY and no error state.
Report reference: dotcms-ui/src/app/portlets/edit-ema/shared/stores/withContentTypeCache.ts:45-52
Potential impact
The UVE quick-edit panel can spin forever after a content-type fetch failure instead of showing a recoverable error state.
Suggested validation
Force the content-type fetch used by quick edit to fail and observe loading/error UI state.
Possible fix
Set an explicit error state and stop loading when the fetch fails; surface the error in the quick-edit UI.
Caveat
This was AI-found by Claude from .scratch/audit/REPORT.md. Please perform secondary validation of correctness, severity, and value before actioning.
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 with dotcms-ui/src/app/portlets/edit-ema/shared/stores/withContentTypeCache.ts:45-52 and trace the content-type fetch used by quick edit. Force that fetch to fail, then observe the loading and error UI state. Done means the quick-edit panel stops spinning and surfaces a recoverable error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100