Soluiton
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react
- Domain
- frontend
Research direction
Start by locating the date comparison in the React datetime component that uses isAfter. Check how today's date is handled, then verify that the date picker accepts today as intended after the comparison is updated.
Written by the indexing model from the issue text.
Description
@Youpinadi Use isSameOrAfter instead of isAfter to use today date.
- Dominant language
- JavaScript
- Stars
- 2k
- Forks
- 858
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from arqex/react-datetime
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
arqex/react-datetime#880 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
arqex/react-datetime#876 · 2 comments · 3 reactions ·
-
Disable past time Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
arqex/react-datetime#874 ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
arqex/react-datetime#873 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
arqex/react-datetime#871 · 3 comments ·
All issues in arqex/react-datetime
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·