Fix coincidence naming of LocalCollection members #957
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.
Purpose
Remove / Fix the coincidentally equal overlappning names in
LocalCollection
of the implementing classes (LocalCalendar and LocalJtxCollection) which extend classes, that already have members of the same name (AndroidCalendar and JtxCollection).<i>LocalCollection
:fun delete(): Boolean
LocalCalendar
: implicit (coincidentally) implemented byAndroidCalendar
:fun delete(): Boolean
and
<i>LocalCollection
:val url: String?
LocalJtxCollection
: implicitly (coincidentally) implemented byJtxCollection
:var url: String?
Short description
In LocalCollection rename:
Update one log statement to use the new way of acquiring the logger.
Checklist