| Summary: | Booking.com hotel booking missing useful information | ||
|---|---|---|---|
| Product: | [Applications] KDE Itinerary | Reporter: | Côme Chilliet <come> |
| Component: | general | Assignee: | Volker Krause <vkrause> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/kitinerary/bc6feff87ad16116f7e069fc9e8bf6c4db13a1e8 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
Côme Chilliet
2020-01-19 11:03:29 UTC
It appears the phone number is actually stored somewhere, because it appears in KDE itinerary on the phone if you click on the booking to get details. Put it does not appear in the calendar event. Is there documentation on how KDE itinerary stores hidden data in calendar event, and how that behaves with other tools? (Like, if I edit the event in korganizer, may I lose data? If I share the calendar event to someone, will he get this hidden data or not?) Right, the full extracted data is stored as a custom property in the ical data. Any compliant ical application should preserve that (and e.g. KOrganizer, Nextcloud and DavDroid do). Ideally all of that should also be visible in the description field, that needs to be fixed. You are also right that this could use more documentation. Git commit bc6feff87ad16116f7e069fc9e8bf6c4db13a1e8 by Volker Krause. Committed on 16/02/2020 at 10:13. Pushed by vkrause into branch 'master'. Improve description for hotel booking ical events Contains all details now, and properly handles multi-traveler bookings. M +1 -1 autotests/calendarhandlerdata/hotel.ics M +33 -7 src/calendarhandler.cpp https://commits.kde.org/kitinerary/bc6feff87ad16116f7e069fc9e8bf6c4db13a1e8 |