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

Parse of tables with arbitrary vertical separators #21

Merged
merged 1 commit into from
Sep 3, 2016

Conversation

dwesely
Copy link
Contributor

@dwesely dwesely commented Sep 3, 2016

  • Identifies vertical separators by recursing through the array to find repeated characters. Does not yet handle spaces as a vertical separator.
  • Allows user-input character for the output separator (so creating csvs is possible, just put a comma in the Custom Separator box before pasting in the text to parse)
  • Added error messages to describe parsing failures.
  • Returns original input (sans separator lines) if a parsing error occurs, so it is less likely that the output will be overwritten automatically if the user changes a setting accidentally.
  • Corrected typo in isSeparatorLine function name.

This is in response to #20, but still does not handle parsing of html or wikimedia tables.

Identifies vertical separators by recursing through the array to find repeated characters. Does not yet handle spaces as a vertical separator.
Allows user-input character for the output separator (so creating csvs is possible, just put a comma in the Custom Separator box before pasting in the text to parse)
Added error messages to describe parsing failures.
Returns original input (sans separator lines) if a parsing error occurs, so it is less likely that the output will be overwritten automatically if the user changes a setting accidentally.
Corrected typo in isSeparatorLine function name.
@ozh ozh merged commit 672019d into ozh:gh-pages Sep 3, 2016
@ozh
Copy link
Owner

ozh commented Sep 3, 2016

🍕

@dwesely dwesely deleted the patch-1 branch September 13, 2018 23:29
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.

None yet

2 participants