You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.The text was updated successfully, but these errors were encountered: