refactor: rename repository/DAO operator get() to fetch()#1447
Merged
Conversation
Replace `operator fun get()` with `fun fetch()` across all repository interfaces, DAO interfaces, their implementations, and all call sites. The get() operator was introduced to satisfy SonarQube but is not idiomatic for complex DB queries — bracket syntax implies simple indexing, not full query execution. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Owner
Author
|
@ThomasKiljanczykDev |
ThomasKiljanczykDev
approved these changes
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
operator fun get(id)withfun fetch(id)on all repository interfaces (MedicineRepository,ReminderRepository,ReminderEventRepository) and DAO interfaces (MedicineDao,ReminderDao,ReminderEventDao)Motivation
The
operator fun get()was introduced to satisfy SonarQube's naming rule, but it is not idiomatic Kotlin for this use case. Bracket-index syntax (repo[id]) implies simple in-memory indexing; these methods perform full Room database queries.fetch()communicates the intent clearly without SonarQube raising a naming issue.🤖 Generated with Claude Code