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

Default implementation for trips creation #33

Closed
pantierra opened this issue Oct 2, 2016 · 3 comments
Closed

Default implementation for trips creation #33

pantierra opened this issue Oct 2, 2016 · 3 comments
Assignees

Comments

@pantierra
Copy link
Contributor

The current trips creation is very much custom for Florianópolis. This issue here is the place to discuss how a default implementation for trips creation could and should look like. Probably it's going to be in the direction of @jamescr Incofer trips creation, as he is using a standard json containing schedule information for all stops. Fenix and Managua is doing more fancy and custom stuff to create a schedule, which the can live (partially) in the respective individual creators.

@pantierra
Copy link
Contributor Author

Trips creator default implementation can only happen after #30.

@pantierra
Copy link
Contributor Author

This is part of PR #99.

@pantierra pantierra added the ready label Jan 6, 2018
@pantierra
Copy link
Contributor Author

Resolved with accepted PR #99

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants