Spec caching: Cache validation results for identical OpenAPI specs to avoid redundant Spectral computation. Use MD5 hash of the entire spec as cache key - when users modify the spec, the hash changes and automatically invalidates the previous cache entry, preventing stale results. Provides immediate benefits when validating the same spec multiple times (e.g., during development iterations).
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | KBach | T422476 [Hypothesis] 5.2.5b: Productionalize API spec linting | |||
| Open | AGhirelli-WMF | T415916 Spec caching: Cache validation results for identical OpenAPI specs | |||
| Open | AGhirelli-WMF | T415917 [SPIKE] Figure out best approach for spec result caching |
Event Timeline
Comment Actions
This task was originally a subtask of T415388: OpenAPI linter - performance and dev-ex improvements. I removed that parent task to simplify the task structure of T422476: [Hypothesis] 5.2.5b: Productionalize API spec linting.