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

[QUESTION] What should happen with empty or invalid bugs field? #16

Open
myrne opened this issue Apr 12, 2013 · 1 comment
Open

[QUESTION] What should happen with empty or invalid bugs field? #16

myrne opened this issue Apr 12, 2013 · 1 comment
Labels

Comments

@myrne
Copy link
Contributor

myrne commented Apr 12, 2013

  1. Remove it always.

  2. Remove it if neither valid url or email were given, or could have been inferred. (current behavior)

  3. Set it to an empty object.

  4. Leave as much fields as is, but

    a. remove offending properties
    b. coerce offending properties to string

Properties are email and url, which must be strings. They could also be validated to be email addresses or http urls, respectively.

@myrne
Copy link
Contributor Author

myrne commented Apr 12, 2013

Currently, normalized bugs field will only have email and url properties, if a valid a value for either was given, or could have been inferred. If bug field exists in the normalized data, it's ensured to have either a url or email property.

@darcyclarke darcyclarke changed the title What should happen with empty or invalid bugs field? [QUESTION] What should happen with empty or invalid bugs field? Jul 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants