Csv import: Refactorings & CsvMapping class#9445
Conversation
For use in the CSV Importer Issue 6772
|
lint check is possibly a remnant as you teased the commits apart? |
mikehardy
left a comment
There was a problem hiding this comment.
Read through it all - seems okay. I'm a bit unclear on major vs minor changes (dispatched where? who would use those handlers + how do you add them to use the facility? I didn't see it in the test so was just a bit unclear). One method name thought, but otherwise LGTM + want to merge
|
I'll add more documentation on the dispatch methods. I'd rather the code spoke for itself than explain it here. Thanks! |
Darkens/lightens the text if a field is disabled usage: android:textColor="@drawable/edit_text_color_enabled_selector" tested on all 4 themes
Adds a lot of noise, and exceptions are expected
The default value for "did" is null when creating a template: Models.defaultTemplate
Also fixes a bug which stems from this, where showActivityFailedScreen() would fail
It's used in a few places now, best to extract
Same name as in Anki Desktop
This documents a special case in the mapping for consumers
Allows mapping from a collection of CSV columns to notes (fields and tags) Also includes Parcelize to allow for simple serialisation of objects to bundles For use in the CSV Import (issue 6772)
Allows users to handle this exception separately
Allows users to handle this exception separately Since we use streams, this exception can be thrown later
97f4197 to
01fd52a
Compare
|
Awaiting re-review (assuming I didn't blow up CI), especially to see if the distinction between major and minor changes has been made more clear. If not, I'll explain the usages and let's brainstorm some better docs. |
|
was waiting on this one for a re-sync on I18n now I'll do an alpha with fresh strings and all the merges of the day |
Pull Request template
Purpose / Description
This breaks off a few changes from #9437 for the CSV import
How Has This Been Tested?
The main change was tested, this should purely be adding code, tested bugfixes and nonfunctional refactorings
Learning (optional, can help others)
I'm unlikely to going to get a large change in in a single PR, and it's better to break it down, despite feeling it's readable as-is
Checklist
ifstatements)