Merged
Conversation
andrehgdias
force-pushed
the
dev-calendar
branch
6 times, most recently
from
0abda3c to
82c476c
Compare
andrehgdias
force-pushed
the
dev-calendar
branch
2 times, most recently
from
56ef449 to
cbc96b0
Compare
andrehgdias
force-pushed
the
dev-calendar
branch
2 times, most recently
from
6cf6ab5 to
735ef14
Compare
andrehgdias
force-pushed
the
dev-calendar
branch
4 times, most recently
from
15dd211 to
6398119
Compare
Ensure compatibility with Kotlin 2.2.20 by removing deprecated methods.
Also improve widget logs. Closes #10408 Co-authored-by: and <and@tutao.de>
…ssing. Refactor CalendarEventDao to use IdTupleCustom, and give IdTupleCustom serialization capability. Rename loadEvents overload to loadEventsFromCache in WidgetDataRepository Co-authored-by: and <and@tutao.de>
Co-authored-by: and <and@tutao.de>
…ing/decoding. android.util.Base64 is designed to throw errors whenever it is run in a test. java.util.Base64 is functionally identical as the android version that uses NO_WRAP. Co-authored-by: and <and@tutao.de>
Co-authored-by: jas
Co-authored-by: and <and@tutao.de>
… events. Co-authored-by: and <and@tutao.de>
Rendering logic changed to use the same high-level logic as on android, including using separate TodayCard and OtherDayCard. DayWithWeekday is also now separate from the EventBody because keeping it there would cause the CalendarIndicator to grow to be too tall and inconsistent in different places. Co-authored-by: and <and@tutao.de> Co-authored-by: bed <bed@tutao.de>
Rearrange the Today Card so the Header Text, all day events, and Event List are in the same column. This ensures that we don't have any unused empty space in case there are no all day events. The New Event button has absolute positioning in the top right part of the card. Co-authored-by: and <and@tutao.de>
Co-authored-by: and <and@tutao.de>
In order to prevent out of memory errors during instance generation, we preemptively try to allocate the necessary memory before pushing to the dates vector in hopes this will reduce SDK crashes(mainly on iOS). This commit also fixes an error with BYWEEKNO applied to ANNUAL events where It would silently skip any event in a series with week number.
Context: When creating event instances for a repeating event there was an implicit limit of how many occurences can becreated, it was defined by u8::MAX. So we never calculated more than 255 instances. For an event that has been created a year ago and repeats daily these events would never be generated. - This fix ensures that all event occurences are always calculated until a given max_date, which now sets the limit. - Public functions have been renamed to calculate_event_occurrences and apply_by_rules. - Also the exported uniffi implementation has changed to be just a small wrapper that gets exported. Closes #10427 Co-authored-by: and <and@tutao.de>
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.
No description provided.