Skip to content

Remove reading agency and route brandingUrl from GTFS data - #6183

Merged
optionsome merged 4 commits into
opentripplanner:dev-2.xfrom
HSLdevcom:remove-branding-url
Nov 1, 2024
Merged

Remove reading agency and route brandingUrl from GTFS data#6183
optionsome merged 4 commits into
opentripplanner:dev-2.xfrom
HSLdevcom:remove-branding-url

Conversation

@tkalvas

@tkalvas tkalvas commented Oct 21, 2024

Copy link
Copy Markdown
Contributor

Summary

Remove the property brandingUrl from the internal data model for agency and route.

Do not read, but still accept, the nonstandard extension brandingUrl for those GTFS files.

Unit tests

Updated the tests to no longer check for brandingUrl.

Documentation

No change.

@tkalvas
tkalvas requested a review from a team as a code owner October 21, 2024 11:48
@optionsome optionsome added the +Bump Serialization Id Add this label if you want the serialization id automatically bumped after merging the PR label Oct 21, 2024
@tkalvas tkalvas changed the title Remove branding url from Agency and ApiLeg Remove brandingUrl from REST API Oct 21, 2024
@tkalvas tkalvas changed the title Remove brandingUrl from REST API Remove agency brandingUrl from REST API Oct 21, 2024
@codecov

codecov Bot commented Oct 21, 2024

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.94%. Comparing base (30216e9) to head (785ac67).
Report is 108 commits behind head on dev-2.x.

Additional details and impacted files
@@              Coverage Diff              @@
##             dev-2.x    #6183      +/-   ##
=============================================
+ Coverage      69.92%   69.94%   +0.02%     
- Complexity     17730    17741      +11     
=============================================
  Files           1996     1997       +1     
  Lines          75416    75435      +19     
  Branches        7717     7722       +5     
=============================================
+ Hits           52734    52763      +29     
- Misses         20000    20004       +4     
+ Partials        2682     2668      -14     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@optionsome
optionsome self-requested a review October 22, 2024 09:35
@t2gran t2gran added this to the 2.7 (next release) milestone Oct 22, 2024

@optionsome optionsome left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We seem to also include brandingUrl from GTFS routes.txt which is also some non-standard field. Should we consider removing that support as well? Seems like at least that's reusing same branding type as netex data.

@tkalvas

tkalvas commented Oct 24, 2024

Copy link
Copy Markdown
Contributor Author

We seem to also include brandingUrl from GTFS routes.txt which is also some non-standard field. Should we consider removing that support as well? Seems like at least that's reusing same branding type as netex data.

I think yes. I didn't notice that, but now that I look at it, it would make sense to remove that at the same time.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I think you can remove the initialization of BRANDING_URL for route in this class so we don't have to update this test class if the brandingUrl gets removed from the OBA library at some point.

@tkalvas tkalvas changed the title Remove agency brandingUrl from REST API Remove agency and route brandingUrl from REST API Oct 25, 2024
@tkalvas tkalvas changed the title Remove agency and route brandingUrl from REST API Remove reading agency and route brandingUrl from GTFS data Oct 25, 2024
@optionsome
optionsome merged commit b162fc5 into opentripplanner:dev-2.x Nov 1, 2024
@optionsome
optionsome deleted the remove-branding-url branch November 1, 2024 10:03
t2gran pushed a commit that referenced this pull request Nov 1, 2024
t2gran pushed a commit that referenced this pull request Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

+Bump Serialization Id Add this label if you want the serialization id automatically bumped after merging the PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants