patternfly / patternfly/patternfly-mcp
Review memo persistence layering
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 11
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 17
Description
As a developer we can review integrating a persistence layer into our memoization layer.
Acceptance criteria
- Review level-of-effort only
Assumptions and question
-
ties into an opt-in persistence layer for API integration updates #148 potentially #182 and #247
-
the memo func already allows a custom cache key, aspects of this can be repurposed to allow a persistence layer into the options or default to current settings
Jira Issue: PF-4522
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 by reviewing the memo function's custom cache-key behavior and the related API integration issues #148, #182, and #247. Document the level of effort for adding an opt-in persistence layer through the memo options or current defaults; completion means the review and estimate are recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100