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

(possibly) allow for completely user defined parsing #163

Open
Tazinho opened this issue Feb 17, 2019 · 2 comments
Open

(possibly) allow for completely user defined parsing #163

Tazinho opened this issue Feb 17, 2019 · 2 comments
Milestone

Comments

@Tazinho
Copy link
Owner

Tazinho commented Feb 17, 2019

It should be possible to add user defined parsing functionality.

To not break the existing parsig_option modus via integers, there could be an alternative via usage of named character vectors. These names and values could form pairs of regular expression patterns and replacements which would be chained and iteratively applied to the string. To enable this, a chain of str_replace_all calls should be wrapped into its own function via a base:::Reduce() call or some while/for conditional.

@Tazinho
Copy link
Owner Author

Tazinho commented Feb 17, 2019

Additionally it should be possible to combine these steps, i.e. providing a vector parsing_option = c("" = "", 1)`, which replaces all ticks first and afterwards applies the default parsing optionality.

@Tazinho
Copy link
Owner Author

Tazinho commented May 25, 2019

hm maybe this is out of scope. any advanced use might be able to write a sequence of gsubs by himself

@Tazinho Tazinho closed this as completed May 25, 2019
@Tazinho Tazinho reopened this Jun 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant