ProfessionalWiki / ProfessionalWiki/PersistentPageIdentifiers
Peformance optimization: only clear parser cache when page contains parser function
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 4
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
We clear the parser cache upon page creation, so our parser function can immediately access the newly generated and saved persistent ID, since that ID is not yet saved on the first parse. Ideally we only do this on pages where the parser function is present.
This is a follow up to
Contributor guide
No contributing guide indexed for this repository
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 reading the issue and the referenced pull request #46 to understand why the parser cache is currently cleared during page creation. Trace the page-creation and parser-function paths in the extension, then verify that cache clearing occurs only for pages containing the parser function while preserving access to the newly saved persistent ID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, performance
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100