Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fare_MasterPricerTravelBoardSearch maximum number of stops? #55

Closed
joakim-malmquist opened this issue Mar 29, 2017 · 7 comments
Closed

Comments

@joakim-malmquist
Copy link

joakim-malmquist commented Mar 29, 2017

In FareMasterPricerTbSearch I can use:
'requestedFlightTypes' => [Client\RequestOptions\FareMasterPricerTbSearch::FLIGHTTYPE_NONSTOP,];
if I don't want any stops at all.

Is it possible to search for example maximum 2 stops?

@DerMika DerMika changed the title FareMasterPricerTbSearch maximum number of stops? Fare_MasterPricerTravelBoardSearch maximum number of stops? Mar 29, 2017
@DerMika
Copy link
Collaborator

DerMika commented Mar 29, 2017

I believe MasterPricer supports it, but my library doesn't support this option yet. I'm currently investigating how to do this in Fare_MasterPricerTravelBoardSearch. I'll keep you informed!

@joakim-malmquist
Copy link
Author

joakim-malmquist commented Mar 31, 2017

I asked my collegues (who work in Amadeus Selling Platform).
The closest thing to a MasterPricer-search is FXD in cryptic mode.
With FXD it isn't possible search by stop, but they have:

/FN for non-stop
/FD for direct
/FC for connecting

i.e. the same thing as in MasterPricer.

@DerMika
Copy link
Collaborator

DerMika commented Apr 1, 2017

I found an option in MasterPricer in the docs called "progressive legs":

Progressive legs enables to request a range of number of connections relative to the minimum connections that exist on Journey Server. This range of number of connections is the progressive legs range.

Progressive legs is triggered by input options:

  • Minimum number of progressive connections (MIC).
  • Maximum number of progressive connections (MAC).

The minimum and maximum number are numeric values from 0 to n.

Is this what you need?

@joakim-malmquist
Copy link
Author

I'll test MIC & MAC. See this as solved if I don't come back. :)

@DerMika
Copy link
Collaborator

DerMika commented Apr 3, 2017

No, the library doesn't support these options yet, I was just asking if these were the options you were looking for - so I could implement them! (in fact, I'm going to implement them anyway, just wanted to hear if these would solve your problem)

@joakim-malmquist
Copy link
Author

Ah, sorry!
Yes please, I would be grateful if you implemented them.
I just thought I could test if it was what I was looking for first - it isn't that hard hack just one option to the xml-code if everything else is already done. :)

@DerMika
Copy link
Collaborator

DerMika commented Apr 3, 2017

Done! You can test it by setting the branch dev-master in your composer.json and doing a composer update.

This feature will be added to the upcoming 1.3.0 release.

See a sample here: https://github.com/amabnl/amadeus-ws-client/blob/master/docs/samples/masterpricertravelboard.rst#progressive-legs

If this doesn't solve your problem, don't hesitate to re-open or create a new issue.

@DerMika DerMika closed this as completed Apr 3, 2017
atomy pushed a commit to mlamm/amadeus-ws-client that referenced this issue Nov 26, 2018
…o master

* commit '59434bf3310b381eeabeb7a956d7d5a8216e9f53':
  VAN-960 | (update) use tracing lib
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants