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

Feature Request: Add Field meta schema property delimiter #204

Open
joneubank opened this issue May 24, 2024 · 1 comment
Open

Feature Request: Add Field meta schema property delimiter #204

joneubank opened this issue May 24, 2024 · 1 comment
Assignees

Comments

@joneubank
Copy link
Contributor

joneubank commented May 24, 2024

When a field is an array, as indicated by the property isArray, it is assumed that when parsing a TSV all values for this field will use the , character as delimiter.

We will add an delimiter property that can provide a different character or string that will be used as the delimiter between values when parsing this field from a TSV.

Rules

  • fields may optionally have a delimiter value
  • values must be a string and cannot be empty (min length 1), no max length (if a long delimiter is required that can be provided)
  • when no value is provided the default used will be ,
@joneubank joneubank self-assigned this May 24, 2024
@joneubank
Copy link
Contributor Author

Updated the ticket description to change the default delimiter to be ,

@joneubank joneubank changed the title Feature Request: Add Field meta schema property arrayDelimiter Feature Request: Add Field meta schema property delimiter Aug 30, 2024
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

No branches or pull requests

1 participant