| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
This makes sure that we have a valid host set. This check is
copies from Soup's private SOUP_URI_IS_VALID() macro.
Add a test for this behavior.
Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/794
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Zero length ranges, such as for events without a DTEND could be
considered to overlap a range if they were at exactly the end of the
range. The end of a range however is the first date that is supposed to
not overlap, so a zero-length range on exactly this point should not be
considered overlapping.
This fixes cases where all-day events from the next month could show up
on the same day of the current month if they did not have a DTEND.
This also adds tests for all possible cases of such zero-length events
overlapping.
Fixes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/701
|
| |
|
|
|
|
| |
Needs more love.
Closes https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/700
|
| |
|
|
| |
This one is actually implemented, what's not implemented is the WebDAV one.
|
| |
|
|
|
|
|
| |
This will be useful for updating events without having
to keep track of the event states.
Add the new API, and also a unit test.
|
| | |
|
| |
|
|
|
| |
More examples of possible dates for events were added to the test cases.
Superset, subset, intersection and no overlap cases are covered.
|
| | |
|
| |
|
|
|
| |
GcalRange is a new structure that represents a time range. It is
always inclusive at the start, and exclusive at the end.
|
| |
|
|
|
| |
It'll be useful to remove entries without knowing their
range.
|
| |
|
|
|
|
|
| |
Using raw integers forces us to select a pre-defined
start and end ranges for the timeline. Since we want
to reuse this data structure on GcalTimeline, make it
a bit more useful.
|
| |
|
|
|
|
|
| |
This improves access to the GcalContext inside GcalManager.
Also, remove test-manager since it only tests that gcal_manager_new()
returns non-NULL.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new source discoverer is a complete overhaul of
the current code. It is async-only, correctly threaded,
and easier to maintain.
A major new feature of this web source discoverer is
that it now pings the server to see if the URL feeds
us back with an iCalendar file.
Furthermore, it continues to use E-D-S WebDAV discovery
functions as a fallback mechanism.
Fixes #380
|
| |
|
|
|
| |
This will be used to write a propert test suite
for the new calendar discoverer code.
|
| | |
|
| |
|
|
|
|
|
| |
Introduce a new GcalStubCalendar class that essentially
removes the ECalClient initialization from GcalCalendar,
and use it as part of a new private library consumed by
the tests.
|
| | |
|
| |
|
|
|
| |
This will greatly help with the transition to GDateTime.
In the future, we can propose these APIs to GLib itself.
|
| |
|
|
|
| |
Otherwise, we're depending on the host machine to run
the tests.
|
| |
|
|
|
| |
Until we have a better control over the system timezone,
let's not hit that issue.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
The unit test that checks GCalManager test fails due to missing
schemas.
This patch allows schemas to be compiled in the build tree and also
sets the environment variables so tests can found them and run
properly.
Additional code and testing from Mohammed Sadiq <sadiq@sadiqpk.org>
|
| |
|
|
|
|
| |
Instead, bring back building all the objects into
calendar itself, and only use the private library
internally.
|
| |
|
|
|
|
|
|
|
|
| |
The first outcome of the test suite. This separation does
not make much sense now, and GcalManager is basically a
holder for all data types.
This commit moves the GSettings to the GcalManager instance
of the application. Of course, in the future, the plan is to
split GcalManager nicely.
|
| |
|
