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

[feature] Add 'trip_short_name' into 'trips.txt' (NTFS v0.10.0) #455

Merged
merged 1 commit into from
Nov 14, 2019

Conversation

woshilapin
Copy link
Contributor

Note: I'm bumping version of transit_model to 0.11.0 since this is a breaking change.

French](https://github.com/CanalTP/ntfs-specification/blob/master/ntfs_changelog_fr.md)).
From the standard, some of the functionalities are not fully supported:
- Management of pathways introduced in version `v0.8` is not supported
- No support for all periodic description (files `grid_calendars.txt`,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be removed since it has been done in #300, #421, #422 and #423.

French](https://github.com/CanalTP/ntfs-specification/blob/master/ntfs_changelog_fr.md)).
From the standard, some of the functionalities are not fully supported:
- Management of pathways introduced in version `v0.8` is not supported
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be removed since it has been done in #398.

Copy link
Member

@datanel datanel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it a PR needed for netex?

Cargo.toml Outdated
@@ -1,7 +1,7 @@
[package]
authors = ["Kisio Digital <[email protected]>", "Guillaume Pinot <[email protected]>"]
name = "transit_model"
version = "0.10.0"
version = "0.11.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's a good idea. If this PR is merged, in the next PR I can also put 0.12.0 and deploys whereas 0.10.0 has never been deployed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, you wouldn't put 0.12.0 because you would check first what is the last released version. The idea is not to increment it everytime you do change something, the idea is just to verify that is coherent with 2 information:

  • what is the last released version
  • what kind of change my PR is doing, and keep or change the next version accordingly

@woshilapin
Copy link
Contributor Author

is it a PR needed for netex?

Yes, we need to populate the trip_short_name.

datanel
datanel previously approved these changes Nov 13, 2019
@mergify mergify bot dismissed datanel’s stale review November 14, 2019 07:55

Pull request has been modified.

@mergify mergify bot merged commit 157ecca into hove-io:master Nov 14, 2019
@datanel datanel changed the title Add 'trip_short_name' into 'trips.txt' (NTFS v0.10.0) [feature] Add 'trip_short_name' into 'trips.txt' (NTFS v0.10.0) Nov 16, 2019
@woshilapin woshilapin deleted the trip_short_name branch November 27, 2019 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants