CenterForDigitalHumanities / CenterForDigitalHumanities/DLA-CMS
Fetch and Cache
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
A note from going between Dunbar Letters and the CMS.
As I added/removed from the Managed Collection, the interfaces would not reflect the change until I went into my Chrome browser settings and manually reset my cache.
I tested this once by waiting a full half hour to see if it would still make me do it, and it did.
This was a lousy user experience.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue by adding and removing items from the Managed Collection, then waiting without manually clearing Chrome's cache. Trace how the interface fetches and caches collection data; done means the interface reflects changes without requiring users to reset their browser cache.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100