fix(verses-api): support multi-verse tafsirs in verses endpoint & Fix eager loading for chapter reciters #718
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR enables support for multi-verse tafsirs in the
/verses/by_keyendpoint.🔧 Fix Summary:
.one_verseconstraint fromVersesPresentertafsir filtering logic.load_tafsirsmethod inVerseFinder, which joins tafsirs by checking whether the verse'sidfalls betweenstart_verse_idandend_verse_id.2:1–2:5).params[:tafsirs], avoiding overhead on unrelated endpoints.Summary for list chapters API
✅ Implementation Notes:
/v4/verses/by_key/2:2?tafsirs=169) without verifying multi-verse coverage due to absence of full DB dump.start_verse_idandend_verse_idare populated in production/staging.