From 3db2799424afb377a89c731323fe45327ebd7f6b Mon Sep 17 00:00:00 2001
From: Daniel Friesel <derf@finalrewind.org>
Date: Sun, 7 Dec 2014 10:39:02 +0100
Subject: [PATCH] documentation
---
Changelog | 5 +++++
lib/Travel/Routing/DE/EFA/Exception.pod | 4 ++--
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/Changelog b/Changelog
index d590475..b5d58cb 100644
--- a/Changelog
+++ b/Changelog
@@ -1,3 +1,8 @@
+git HEAD
+
+ * Travel::Routing::DE::EFA::Exception::Ambiguous: Add post_value accessor
+ which contains the ambiguous input value
+
Travel::Routing::DE::VRR 2.08 - Wed Oct 08 2014
* efa: Add -l / --list option
diff --git a/lib/Travel/Routing/DE/EFA/Exception.pod b/lib/Travel/Routing/DE/EFA/Exception.pod
index 5ec2991..d01087a 100644
--- a/lib/Travel/Routing/DE/EFA/Exception.pod
+++ b/lib/Travel/Routing/DE/EFA/Exception.pod
@@ -45,8 +45,8 @@ We got no parsable data from the EFA service
=head2 Travel::Routing::DE::EFA::Exception::Ambiguous
Our request contained ambiguous data. B<post_key> contains the relevant POST
-key, B<possibilities> is a comma-separated string of possible key values (as
-reported by the EFA service).
+key and B<post_value> the corresponding input value. B<possibilities> is a
+pipe-separated string of acceptable values reported by the EFA service.
=head2 Travel::Routing::DE::EFA::Exception::NoConnections
--
GitLab