I am using calendar-import-export in a comparably »extreme« way that involves re-importing an ical file from scratch, i. e. with explicitly deleting any pre-existing entry.
Currently I achieve this indirectly: export, import for deletion; later import for addition.
However this is burdening enough that I am willing to extend calendar-import-export accordingly.
Before attempting this I would consider to transform the whole app from Java to Kotlin using the facilities of Android Developer Studio. Although this by itself does not resolve any architectural problem, the code’s readability and maintainability might improve over time. @dschuermann @jgriffiths You seem to be the most active contributors, I won’t do this without your consensus. What do you think? Prior to that I am willing to go through existing pending pull requests and review them.
I am using calendar-import-export in a comparably »extreme« way that involves re-importing an ical file from scratch, i. e. with explicitly deleting any pre-existing entry.
Currently I achieve this indirectly: export, import for deletion; later import for addition.
However this is burdening enough that I am willing to extend calendar-import-export accordingly.
Before attempting this I would consider to transform the whole app from Java to Kotlin using the facilities of Android Developer Studio. Although this by itself does not resolve any architectural problem, the code’s readability and maintainability might improve over time. @dschuermann @jgriffiths You seem to be the most active contributors, I won’t do this without your consensus. What do you think? Prior to that I am willing to go through existing pending pull requests and review them.