Case-sensitivity of filenames #297
Comments
|
I (hoped) it was explicit from all the examples. But I guess you have found a producer that uses capitals? |
|
I was also obvious for me ;)
But indeed, a producer came with a capital, and we can’t really point to
paragraph of the specification
…On Wed, 15 Dec 2021 at 15:46, Stefan de Konink ***@***.***> wrote:
I (hoped) it was explicit from all the examples. But I guess you have
found a producer that uses capitals?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#297 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAC7SZ3NU3BCHTC5XKEZ4LURCS4JANCNFSM5KDZV7GA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
We can add it as a point to the "File Requirements" section. Perhaps we can amend the 3rd point to say:
|
|
Seems good for me. What would be the following steps to actually amend that point? |
Think you want to create a pull request, with an immediate vote, and announce it on the mailinglist. |
Tristramg
added a commit
to Tristramg/transit
that referenced
this issue
Dec 20, 2021
|
@Tristramg Please see the specification amendment process. AFAIK immediate votes are not the norm when opening a pull request (usually 7 days of discussion are needed first). Also voting can only be called by the advocate of the pull request. At any rate, I almost think we can merge this one directly since it is a fairly minor and straightforward clarification? |
scmcca
pushed a commit
that referenced
this issue
Jan 28, 2022
scmcca
pushed a commit
to MobilityData/transit
that referenced
this issue
Feb 11, 2022
commit 2e6887e Author: scmcca <[email protected]> Date: Wed Feb 2 12:42:10 2022 -0500 [Formatting fix] Add newlines before lists Improved syntax for different markdown parsers commit 0033573 Author: Tristram Gräbener <[email protected]> Date: Fri Jan 28 15:54:00 2022 +0100 Specify that the filename are case sensitive (google#300) Closes google#297 commit 23d877e Author: scott christian mccallum <[email protected]> Date: Tue Jan 18 19:09:46 2022 -0500 "Fields" and "Values" as non-header (google#302)
isabelle-dr
pushed a commit
to MobilityData/transit
that referenced
this issue
Dec 19, 2023
* Squashed commit of the following: commit 2e6887e Author: scmcca <[email protected]> Date: Wed Feb 2 12:42:10 2022 -0500 [Formatting fix] Add newlines before lists Improved syntax for different markdown parsers commit 0033573 Author: Tristram Gräbener <[email protected]> Date: Fri Jan 28 15:54:00 2022 +0100 Specify that the filename are case sensitive (google#300) Closes google#297 commit 23d877e Author: scott christian mccallum <[email protected]> Date: Tue Jan 18 19:09:46 2022 -0500 "Fields" and "Values" as non-header (google#302) * Squashed commit of the following: commit 9d5ebf1 Author: Guillaume Campagna <[email protected]> Date: Tue Jul 26 17:09:35 2022 -0400 Add trip-to-trip transfers with in-seat option (google#303) * Add trip-to-trip transfers with in-seat option * Fix stop_id are **Conditionally Required** and formatting * Add clarification about potential conflict * Fix typo Co-authored-by: Leonard Ehrenfried <[email protected]> Co-authored-by: Nicholas Paun <[email protected]> Co-authored-by: Leonard Ehrenfried <[email protected]> commit a132709 Author: McKenzie Maidl <[email protected]> Date: Tue Jul 26 13:58:04 2022 -0700 addition of cause_detail and effect_detail to the spec (google#332) commit 8993a24 Author: Zsombor Welker <[email protected]> Date: Mon Jul 25 14:49:40 2022 +0200 Add WheelchairAccessible documentation (google#340) * Update README.md (#63) * issue templates * update use cases section * update contact links * rename * Delete .github/ISSUE_TEMPLATE/spec_improvement.yml --------- Co-authored-by: scmcca <[email protected]> Co-authored-by: omar-kabbani <[email protected]> Co-authored-by: Emma Jae Blue <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The specifications says that the columns names are case-sensitive.
However nothing is specified for filenames. Should a
Routes.txtbe a valid file for the routes or not.I have no strong opinion here, but I believe the specification should be explicit if can be allowed or not.
The text was updated successfully, but these errors were encountered: