feat: re-export external types from the API as part of the API #923
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today, all users of
transit_model
can't depend only ontransit_model
in theirCargo.toml
because if one of the API returns aNaiveDate
, or anyIdx
, the use basically needs to also importchrono
andtyped_index_collection
. On top of that, it must find and import the exact same version of the dependency that the one declared intransit_model
(or else, might face compilation errors).Let's be more explicit on the API we expose. Note that I did not make an exhaustive research of all the things that we must re-export, only a brief dive to catch most of them. It's a step forward, might not be a perfect step though 🤷