You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could move this method over to @opentripplanner/core-utils/src/query if that would be helpful.
Randolph: ... Would be great to get a util that does the opposite (query object to OTP-API string) put in the OTP-UI. I did try and extract the logic from that api module and it got kind of tricky. We would use that module at least twice. Once when talking with the OTP API and another when generating the query params string for trimet.org urls when we need one. If you need anymore details, just let me know. Thanks.
evansiroky
ok ... Can you create a github issue please?
The text was updated successfully, but these errors were encountered:
From this Slack conversation: https://trimet-mod-sandbox.slack.com/archives/CRC48NTJ4/p1579567951000400
There definitely is more nuance to constructing the query params. That logic is contained within here: https://github.com/opentripplanner/otp-react-redux/blob/906d9226553cbbdd83cf455986f199c5a6964f72/lib/actions/api.js#L164-L246
I could move this method over to @opentripplanner/core-utils/src/query if that would be helpful.
Randolph: ... Would be great to get a util that does the opposite (query object to OTP-API string) put in the OTP-UI. I did try and extract the logic from that api module and it got kind of tricky. We would use that module at least twice. Once when talking with the OTP API and another when generating the query params string for trimet.org urls when we need one. If you need anymore details, just let me know. Thanks.
evansiroky
ok ... Can you create a github issue please?
The text was updated successfully, but these errors were encountered: