fix: extend BCE regex from 5 to 7 digits for paleolithic dates#5
Open
e-huseyin wants to merge 1 commit into
Open
fix: extend BCE regex from 5 to 7 digits for paleolithic dates#5e-huseyin wants to merge 1 commit into
e-huseyin wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The BCE_START_REGEX was limited to 5 digits (max 99,999 BCE), which prevented parsing dates commonly used in archaeology, such as
800000 BCE - 300000 BCE(Lower Paleolithic).The existing comment even noted this possibility: > "5,6 digits could be used for paleolithic but its overkill"
As an archaeologist building a timeline of prehistoric periods in, I hit this limit directly. Changing
{1,5}to{1,7}supports dates up to 9,999,999 BCE — covering all of human prehistory — with no performance impact.