Travel::Routing::DE::EFA::Route::Message(3) contains a message related to a

SYNOPSIS


for my $m ($routepart->regular_notes, $routepart->current_notes) {
if ($m->is_detailed) {
printf("%s: %s\n", $m->subtitle, $m->subject);
}
else {
say $m->summary;
}
}

VERSION

version 2.14

DESCRIPTION

Travel::Routing::DE::EFA::Route::Message contains information about a specific route or route part, such as wheelchair accessibility, unscheduled route diversions and cancelled stops. Often, this information is not used in the backend's route calculation, so a message may invalidate a certain route or route part.

There are two types of messages provided by the backend: oneliners and detailed messages. There is no known distinction regarding their type or content. Also, there are some other backend-provided fields not yet covered by this module, so expect changes in future releases.

A oneline message consists of a single string which can be accesed using subject or summary and its is_detailed accessor returns false.

A detailed message has a subject, subtitle, summary and detailed HTML content.

METHODS

ACCESSORS

$message->is_detailed
True if all accessors (fields) are set, false otherwise. When this field is false, only summary and subject are set (and they will return the same string).
$message->summary
Message summary.
$message->subject
Message subject. May be the same string as the subtitle.
$message->subtitle
Message subtitle. May be the same string as the summary.
$message->raw_content
Raw HTML content. May contain information not available via any other accessor.

DIAGNOSTICS

None.

DEPENDENCIES

None.

BUGS AND LIMITATIONS

This module does not yet provide access to all data provided by the backend. Most notably, raw_content is not properly parsed yet.

AUTHOR

Copyright (C) 2015 by Daniel Friesel <[email protected]>

LICENSE

  0. You just DO WHAT THE FUCK YOU WANT TO.