Bug 436976 - OUI app, kitinerary takes care of half of the round trip in the confirmation mail
Summary: OUI app, kitinerary takes care of half of the round trip in the confirmation ...
Status: RESOLVED FIXED
Alias: None
Product: KDE Itinerary
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Volker Krause
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-12 14:32 UTC by Philippe ROUBACH
Modified: 2021-05-15 08:21 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 21.04.2
Sentry Crash Report:


Attachments
the round trip confirmation mail (161.32 KB, application/mbox)
2021-05-12 14:32 UTC, Philippe ROUBACH
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe ROUBACH 2021-05-12 14:32:25 UTC
Created attachment 138364 [details]
the round trip confirmation mail

SUMMARY


STEPS TO REPRODUCE
1. With "OUI" app buy a round trip ticket
2. 
3. 

OBSERVED RESULT

the kitinerary header of the confirmation mail displays only the first part of the trip
if you click on "calendar" button only the first part is recorded as an event.

EXPECTED RESULT

the kitinerary header of the confirmation mail displays the two parts of the round trip
if you click on "calendar" button the two parts are recorded as an event

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

kde apps 21.04.0
Comment 1 Volker Krause 2021-05-15 08:13:06 UTC
Git commit 947babff7907c6cbe2ed099b1d91cb763f1d7f64 by Volker Krause.
Committed on 15/05/2021 at 08:12.
Pushed by vkrause into branch 'release/21.04'.

Improve handling of multi-leg and return tickets in Oui.sncf summary emails

For multi-leg journeys all involved trains are listed here, but neither
locations nor times of the involved connections. Since we cannot identify
all elements of journey correctly then, don't pretend we do that and ignore
the train number in that case. This also avoids merge problems when more
details become available later by other means.

Return journeys were not handled at all yet, we can use the same logic for
that with just different XPath search patterns.
FIXED-IN: 21.04.2

M  +33   -10   src/lib/extractors/sncf.js

https://invent.kde.org/pim/kitinerary/commit/947babff7907c6cbe2ed099b1d91cb763f1d7f64
Comment 2 Philippe ROUBACH 2021-05-15 08:21:12 UTC
thanks