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

Forbid empty Strings #636

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Forbid empty Strings #636

wants to merge 1 commit into from

Conversation

tdelmas
Copy link
Contributor

@tdelmas tdelmas commented May 16, 2024

Fix #600

See also https://mobilitydata-io.slack.com/archives/CNXA9ASBV/p1715598631556219

What is the proposal?

Specify that strings (including IDs) MUST NOT be empty.

Is this a breaking change?

  • Yes
  • No
  • Unsure

Which files are affected by this change?

All of them (because of the IDs)

Examples of affected feeds

https://mobilitydata-io.slack.com/archives/CNXA9ASBV/p1708449123435399?thread_ts=1708429919.754579&cid=CNXA9ASBV

Examples for feeds currently using (very few) empty station names:

@tdelmas
Copy link
Contributor Author

tdelmas commented May 30, 2024

Before submitting to a vote, do you think that change could be in 3.2 ? It is technically a breaking change, but I think it worth it to improve the GBFSv3.
Thoughts?

@richfab
Copy link
Contributor

richfab commented May 30, 2024

Hi @tdelmas,

I think we should avoid making an exception to the change process.

If the community wants to make the change in v3.2-RC, we could consider:

  1. Making the change non-breaking with "SHOULD not be empty" instead of "MUST not be empty".
  2. Asking producers to fill in the missing values.

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

Successfully merging this pull request may close these issues.

Required strings
2 participants