-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Persist line/station preferences #5
Comments
Ideal storage mechanism is Azure Table Storage or Azure DocumentDB.. |
Dependent on #15. |
martincostello
added a commit
that referenced
this issue
Mar 12, 2017
Add start of implementation of storing line preferences. Currently renders the line names for the supported modes of travel and does a postback which is not persisted. Text not yet stored in resources as UI is still in flux. Relates to #5.
martincostello
added a commit
that referenced
this issue
Mar 12, 2017
Initial support for persisting line preferences for a user. Add parameter validation to controller endpoints. Use strongly-typed objects for the TfL API service. Still requires localisation. Relates to #5.
Lines resolved by 94d9fa4; still need stations. |
Station support moved to #42. Now completed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow the user to persist their line and, optionally their station, preferences in the companion site.
This will then enable functionality for the skill to find the preferences for the linked account for their commute (martincostello/alexa-london-travel#9).
The text was updated successfully, but these errors were encountered: