scrapinghub/dateparser

Add support for other words ("decade", "fortnight", "century"...)

Open

#725 opened on Jun 25, 2020

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Python (2,318 stars) (443 forks)batch import
good first issue

Description

There are some words that can be added to the library:

  • Decade: 10 years (2 decade --> 20 years, ...)
  • Fortnight: 14 days (Example: "a fortnight ago")
  • Century: 100 years (Example: "a century ago", "two centuries ago")

It's not necessary to put them all in a unique PR, you can submit just one of them. Just take in mind that it should support "next decade", "last decade", "a decade ago", "in a decade", but also "two decades ago".

Contributor guide

Tech stack
python
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Pythonfamiliarity with dateparser library
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Examine the existing implementation of time units like 'year' or 'month' in the dateparser codebase, likely in files such as `dateparser/conf.py` or `dateparser/search.py`. Identify the data structures that map words to durations and add new entries for 'decade', 'fortnight', and 'century' following the same pattern. Ensure support for plural forms and modifiers like 'a', 'next', 'last', 'in a', and numeric prefixes. After implementing, add corresponding tests in the test suite.
Add support for other words ("decade", "fortnight", "century"...) · scrapinghub/dateparser#725 | Good First Issue