summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* docs: Add a link to the GWeather referenceebassi/add-logoEmmanuele Bassi2021-11-181-0/+1
|
* docs: Add the libgweather logoEmmanuele Bassi2021-11-182-0/+33
| | | | We have a simple project logo, now.
* docs: Divide migration guide in twoEmmanuele Bassi2021-11-171-1/+11
| | | | | | We have one section that lists changes that can be performed while still using GWeather 3.x, and another section that outlines changes that can only be done when porting to GWeather 4.
* docs: Fix links to GWeatherLocationEmmanuele Bassi2021-11-173-3/+3
| | | | | It's an object type, now, and gi-docgen has gotten fussy about wrong fragments.
* Remove trailing newlines from logging functionsEmmanuele Bassi2021-11-174-27/+21
| | | | | All the GLib logging functions automatically append a newline to the given string.
* tests: Turn random output into test messagesEmmanuele Bassi2021-11-171-33/+25
| | | | | | | The g_test_message() function ensures that the output does not break any TAP harness. Replacing the random g_print/g_debug/g_message with g_test_message() has the additional benefit of not requiring a custom log handler.
* metar: Plug a memory leakEmmanuele Bassi2021-11-171-0/+5
| | | | | We need to free the uri object, regardless of whether it is a SoupUri or a GUri.
* Remove GWeatherLocation reference wrappersEmmanuele Bassi2021-11-173-38/+12
| | | | | Document that GWeatherLocation is a full GObject type, and that you should use the GObject API to acquire and release references.
* Turn GWeatherLocation into a proper GObjectEmmanuele Bassi2021-11-177-244/+317
| | | | | | We want to make it easier to use GWeatherLocation inside data structures like GListModel implementations. It's also easier to use from language bindings, as now objects will have a clear life time.
* Update Portuguese translationHugo Carvalho2021-11-161-15/+16
|
* Check that gweather_location_get_world() doesn't return NULLEmmanuele Bassi2021-11-121-5/+17
| | | | While it's extremely unlikely, it's still possible.
* Remove unused assignmentEmmanuele Bassi2021-11-121-3/+2
| | | | | The iteration variable is re-initialised immediately as part of the loop.
* Remove unused assignmentEmmanuele Bassi2021-11-121-9/+12
| | | | | The `esat` variable is only ever used in one branch when calculating the dew point.
* Clean up the metric/imperial unit detectionEmmanuele Bassi2021-11-121-14/+17
| | | | | Move the fallback declaration outside the nl_langinfo() query, and use a more descriptive message in case of localisation error.
* Do not return an additional referenceEmmanuele Bassi2021-11-121-1/+1
| | | | | When finding the nearest city we already acquire a reference on the location; we should not acquire an additional one.
* Keep a reference while iterating on a locationEmmanuele Bassi2021-11-121-1/+14
| | | | | This avoids an unused variable declaration when the first argument is NULL.
* Avoid a potential NULL dereferenceEmmanuele Bassi2021-11-121-12/+20
| | | | | | | | | | | | When asynchronously querying for the nearest location at the given location we should keep a reference on the parent location, in case it goes away mid-search. This is especially important when passing `NULL` as the parent location: the current code uses a `g_autoptr()` to store the "world" node, and then passes the pointer unmodified; if that happened, the location would be released at the end of the function, and the asynchronously invoked callback would get a garbage pointer.
* Update Croatian translationGoran Vidović2021-11-121-299/+300
|
* Update Croatian translationGoran Vidović2021-11-121-2/+8
|
* build: Use the library() target to populate the pkg-config fileEmmanuele Bassi2021-11-111-8/+2
| | | | | | Instead of specifying the required dependencies manually. Fixes: #152
* Run the code base through the style formatterEmmanuele Bassi2021-11-106-37/+41
| | | | Ensure that the changes are consistent.
* ci: Build against both libsoup2 and libsoup3Patrick Griffis2021-11-101-0/+60
|
* tests: Use g_assert_no_error()Patrick Griffis2021-11-101-1/+1
|
* tests: Fix double freePatrick Griffis2021-11-101-2/+0
|
* build: Include libsoup api version in pkg-configPatrick Griffis2021-11-101-1/+15
|
* Port to libsoup3Daniel Kolesa2021-11-1010-40/+315
|
* Update Occitan translationQuentin PAGÈS2021-11-071-302/+303
|
* Update Friulian translationFabio Tomat2021-11-071-301/+303
|
* Update Friulian translationFabio Tomat2021-11-071-56/+8
|
* Update Persian translationDanial Behzadi2021-11-071-294/+298
|
* Update Persian translationeshagh shahidani2021-11-071-4/+7
|
* Update Portuguese translationHugo Carvalho2021-11-061-301/+305
|
* Update Swedish translationAnders Jonsson2021-11-061-65/+9
|
* Update Ukrainian translationYuri Chornoivan2021-11-051-301/+304
|
* Update Ukrainian translationYuri Chornoivan2021-11-051-142/+43
|
* Update Occitan translationQuentin PAGÈS2021-10-311-19988/+19938
|
* Update Latvian translationRūdolfs Mazurs2021-10-251-231/+258
| | | | (cherry picked from commit 00011f35a6e7a419d88b1bcb99b09d248d6bb4ca)
* Use the appropriate Unicode for temperature unitsEmmanuele Bassi2021-10-241-14/+26
| | | | | | | | | | | The U+2103 DEGREE CELSIUS and U+2109 DEGREE FAHRENHEIT code points are compatibility characters, and there's no guarantee that they will actually exist. The preferred way to present degrees Celsius and Fahrenheit is to use U+00B0 and the letter C and F, respectively. Fixes: #8
* Add Location "Blagoveschensk", city in RussiaКирилл Шестаков2021-10-241-0/+13
|
* Plug memory leakEmmanuele Bassi2021-10-241-1/+1
| | | | | | | | The GWeather.Info.get_location_name() returns a string with full ownership. Instead of going through the public API, we can get the location name directly from the data structure. Fixes: #80
* build: Use a variable for the pkg-config nameEmmanuele Bassi2021-10-211-3/+5
| | | | | It seems that some of the targets using the pkg-config file name do not like it when we directly pass a formatted string object.
* ci: Run jobs on merge requestsEmmanuele Bassi2021-10-191-0/+3
|
* ci: Run style check only on merge requestsEmmanuele Bassi2021-10-191-1/+1
|
* ci: Post the style check output as a comment on the MREmmanuele Bassi2021-10-191-11/+12
| | | | If the job is part of a merge request.
* ci: Add curl to the style check packagesEmmanuele Bassi2021-10-191-1/+1
|
* ci: Redirect clang-format-diff output to a fileEmmanuele Bassi2021-10-191-1/+16
| | | | And print the contents of the file. We are going to need this later.
* Ignore gi-docgen's subprojectEmmanuele Bassi2021-10-161-0/+1
| | | | If we clone it, we don't really need it to mess with Git.
* build: Allow disabling the tests and toolsEmmanuele Bassi2021-10-162-2/+6
| | | | | Projects that depend on libgweather and build it as part of their Flatpak manifest should have the option to skip building the tests.
* docs: Mention clang-formatEmmanuele Bassi2021-10-171-1/+18
| | | | | Contributors should use clang-format to ensure that their code fits in with the rest of the code base.
* build: Require pygobjectEmmanuele Bassi2021-10-171-0/+1
| | | | | | | The locations binary blob generator depends on pygobject, so we should actually check for its presence during the configuration phase. Otherwise the configuration will pass, and then the build will fail, and we're going to look bad.
View Lorry Controller Status