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 would be nice to be able to pass in real-world opening hours data that may have some typos and have this library automatically handle that.
Maybe a more complex solution would be better but for now an easy solution to this would be to change some of the patterns that currently use CaselessMatch for parsing so they can tolerate a certain number of incorrect characters and still be considered valid.
This "ignore up to x typos" functionality does not currently exist in this specific class in pyparsing, although it exists in other classes (CloseMatch if i recall correctly). There is currently an open PR in pyparsing to add this functionality.
The text was updated successfully, but these errors were encountered:
It would be nice to be able to pass in real-world opening hours data that may have some typos and have this library automatically handle that.
Maybe a more complex solution would be better but for now an easy solution to this would be to change some of the patterns that currently use
CaselessMatch
for parsing so they can tolerate a certain number of incorrect characters and still be considered valid.This "ignore up to x typos" functionality does not currently exist in this specific class in pyparsing, although it exists in other classes (
CloseMatch
if i recall correctly). There is currently an open PR in pyparsing to add this functionality.The text was updated successfully, but these errors were encountered: