jordi fita mas bd124581cc Handle null strings in I18nInput.FillArray ... Until now i always had the translations be empty strings if some columns did not have the full translation, but this is going too far on the non-NULL policy: surely they have a translations, but we do not know it yet; this is the exact type of situations NULL values are for. Besides the philosophical distinction, having empty strings instead of NULLs is less practical, because i no longer can user coalesce() to retrieve the default language text in case the translation for that particular field is not available, even if the row for a locale exists. In time i will change all _i18n relations, but for now only these from campsite follow the “new policy”.		2024-01-26 22:31:11 +01:00
..
checkbox.go	Add the Active field to the campsite type’s edit form and function	2023-08-14 11:43:58 +02:00
file.go	Add cover media to campsite types	2023-09-10 03:04:18 +02:00
handle.go	Add the edit form for services	2023-09-25 20:10:33 +02:00
input.go	Handle null strings in I18nInput.FillArray	2024-01-26 22:31:11 +01:00
media.go	Manage all media uploads in a single place	2023-09-21 01:56:44 +02:00
select.go	Add public pages for each individual accommodation	2024-01-26 22:27:54 +01:00
validator.go	Add the payment form to admin	2023-10-27 16:08:13 +02:00